LearnToEarn

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the TermMax docs last night, specifically the TMX utility and risk sections. Total supply is fixed at 1B, with Community at 150M (15%). Initial circulation sits around 20%.

The part that stuck with me is how $TMX holders can stake for sTMX (protocol FT tokens denominated in TMX) or LP it on something like PancakeSwap. Staking rewards can come from the Community allocation plus a slice of Treasury funds. Those Treasury inflows are supposed to come from trading fees on FT/XT tokens, protocol fees on borrowing, liquidation fees, and other sources. It looks like a way to tie long-term holders to actual protocol revenue, but I’m still unclear how much of the Treasury actually flows to stakers versus other uses.

Enhanced governance rights for stakers include adjusting market risk parameters and curator whitelisting. That raises questions about how decentralized the process really is once live. On the risk side, they openly list smart-contract risk (audits, competitions, monitoring, and bounties notwithstanding), dual-oracle dependency that could still fail, network congestion, price volatility, liquidity risk, regulatory uncertainty, and competition from other fixed-rate protocols.

I’m left wondering how the dual-oracle setup handles edge cases in practice, and whether the enhanced governance for sTMX holders meaningfully shifts control or mostly refines parameters set by the team. Anyone who’s dug into the contracts or fee flows how do you read the sustainability of the Treasury-to-staker path?

#termmax @TermMax

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the TermMax docs last night, specifically the TMX utility and risk sections. Total supply is fixed at 1B, with Community at 150M (15%). Initial circulation sits around 20%.

The part that stuck with me is how $TMX holders can stake for sTMX (protocol FT tokens denominated in TMX) or LP it on something like PancakeSwap. Staking rewards can come from the Community allocation plus a slice of Treasury funds. Those Treasury inflows are supposed to come from trading fees on FT/XT tokens, protocol fees on borrowing, liquidation fees, and other sources. It looks like a way to tie long-term holders to actual protocol revenue, but I’m still unclear how much of the Treasury actually flows to stakers versus other uses.

Enhanced governance rights for stakers include adjusting market risk parameters and curator whitelisting. That raises questions about how decentralized the process really is once live. On the risk side, they openly list smart-contract risk (audits, competitions, monitoring, and bounties notwithstanding), dual-oracle dependency that could still fail, network congestion, price volatility, liquidity risk, regulatory uncertainty, and competition from other fixed-rate protocols.

I’m left wondering how the dual-oracle setup handles edge cases in practice, and whether the enhanced governance for sTMX holders meaningfully shifts control or mostly refines parameters set by the team. Anyone who’s dug into the contracts or fee flows how do you read the sustainability of the Treasury-to-staker path?

#termmax @TermMax

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the TermMax docs last night, specifically the TMX utility and risk sections. Total supply is fixed at 1B, with Community at 150M (15%). Initial circulation sits around 20%.

The part that stuck with me is how $TMX holders can stake for sTMX (protocol FT tokens denominated in TMX) or LP it on something like PancakeSwap. Staking rewards can come from the Community allocation plus a slice of Treasury funds. Those Treasury inflows are supposed to come from trading fees on FT/XT tokens, protocol fees on borrowing, liquidation fees, and other sources. It looks like a way to tie long-term holders to actual protocol revenue, but I’m still unclear how much of the Treasury actually flows to stakers versus other uses.

Enhanced governance rights for stakers include adjusting market risk parameters and curator whitelisting. That raises questions about how decentralized the process really is once live. On the risk side, they openly list smart-contract risk (audits, competitions, monitoring, and bounties notwithstanding), dual-oracle dependency that could still fail, network congestion, price volatility, liquidity risk, regulatory uncertainty, and competition from other fixed-rate protocols.

I’m left wondering how the dual-oracle setup handles edge cases in practice, and whether the enhanced governance for sTMX holders meaningfully shifts control or mostly refines parameters set by the team. Anyone who’s dug into the contracts or fee flows how do you read the sustainability of the Treasury-to-staker path?

#termmax @TermMax

I went back through the Dusk documentation last night, and I came away more interested in the design questions than technical claims.

The first thing that clicked was the split between Moonlight and Phoenix. Moonlight is account-based, with a public key, nonce and balance, while Phoenix uses UTXOs as “notes” inside a Merkle tree. Moonlight transaction fields include from, to, value, nonce, deposit, data, gas_limit, gas_price and signature, with maximum gas calculated as gas_limit × gas_price.

Phoenix gets interesting. It uses the Jubjub curve, with public keys (A,B), secret keys (a,b), and a view key (a,B). The note structure includes type, com, enc, npk, R and encsender. The one-time note key is derived as npk = H(rA)G + B, while the spending key is nsk = H(aR) + b.

I’m still trying to understand the trust boundary around ZK proof generation and delegated scanning. The documentation says third parties can generate proofs or scan using view keys without getting spending authority, but where are the failure points?

And with nullifiers, recent Merkle roots, and gas handled inside the proof, how does this behave under adversarial network conditions? Which parts are decentralized, and which assumptions should users scrutinize?

#dusk $DUSK @Dusk

I went back through the TermMax docs last night, specifically the TMX utility and risk sections. Total supply is fixed at 1B, with Community at 150M (15%). Initial circulation sits around 20%.

The part that stuck with me is how $TMX holders can stake for sTMX (protocol FT tokens denominated in TMX) or LP it on something like PancakeSwap. Staking rewards can come from the Community allocation plus a slice of Treasury funds. Those Treasury inflows are supposed to come from trading fees on FT/XT tokens, protocol fees on borrowing, liquidation fees, and other sources. It looks like a way to tie long-term holders to actual protocol revenue, but I’m still unclear how much of the Treasury actually flows to stakers versus other uses.

Enhanced governance rights for stakers include adjusting market risk parameters and curator whitelisting. That raises questions about how decentralized the process really is once live. On the risk side, they openly list smart-contract risk (audits, competitions, monitoring, and bounties notwithstanding), dual-oracle dependency that could still fail, network congestion, price volatility, liquidity risk, regulatory uncertainty, and competition from other fixed-rate protocols.

I’m left wondering how the dual-oracle setup handles edge cases in practice, and whether the enhanced governance for sTMX holders meaningfully shifts control or mostly refines parameters set by the team. Anyone who’s dug into the contracts or fee flows how do you read the sustainability of the Treasury-to-staker path?

#termmax @TermMax

I went back through the Dusk documentation last night, and the incentive section made me slow down and read it twice.

What I first understood as a simple validator reward is more nuanced. Block rewards come from newly minted DUSK and transaction fees, with 80% going to the block generator, 10% to the voting committee, and 10% to Dusk. The generator’s 80% is split into a fixed 70% and a variable 10%, where the variable part depends on votes included in the block certificate. Voter rewards are based on credits, so voting power and incentives are closely connected.

That raised a question for me: does rewarding higher-credit voters strengthen participation, or could it gradually concentrate influence among already-strong provisioners?

The security side is also interesting. Minor faults can lead to suspension and soft slashing, while major faults such as invalid blocks, double voting, or conflicting blocks can trigger hard slashing.

Then I reached transactions. Dusk uses two models: Moonlight, an account-based model with public keys, and Phoenix, a UTXO-based model using ZK proofs for privacy. The contrast is clear, but I’m still wondering how these two models affect long-term decentralization and governance in practice.

How do you view the trade-off between voter credits, penalties, and decentralization?

@Dusk #dusk $DUSK

I went back through the Dusk documentation last night, and the incentive section made me slow down and read it twice.

What I first understood as a simple validator reward is more nuanced. Block rewards come from newly minted DUSK and transaction fees, with 80% going to the block generator, 10% to the voting committee, and 10% to Dusk. The generator’s 80% is split into a fixed 70% and a variable 10%, where the variable part depends on votes included in the block certificate. Voter rewards are based on credits, so voting power and incentives are closely connected.

That raised a question for me: does rewarding higher-credit voters strengthen participation, or could it gradually concentrate influence among already-strong provisioners?

The security side is also interesting. Minor faults can lead to suspension and soft slashing, while major faults such as invalid blocks, double voting, or conflicting blocks can trigger hard slashing.

Then I reached transactions. Dusk uses two models: Moonlight, an account-based model with public keys, and Phoenix, a UTXO-based model using ZK proofs for privacy. The contrast is clear, but I’m still wondering how these two models affect long-term decentralization and governance in practice.

How do you view the trade-off between voter credits, penalties, and decentralization?

@Dusk #dusk $DUSK

I went back through the Dusk documentation last night, and the incentive section made me slow down and read it twice.

What I first understood as a simple validator reward is more nuanced. Block rewards come from newly minted DUSK and transaction fees, with 80% going to the block generator, 10% to the voting committee, and 10% to Dusk. The generator’s 80% is split into a fixed 70% and a variable 10%, where the variable part depends on votes included in the block certificate. Voter rewards are based on credits, so voting power and incentives are closely connected.

That raised a question for me: does rewarding higher-credit voters strengthen participation, or could it gradually concentrate influence among already-strong provisioners?

The security side is also interesting. Minor faults can lead to suspension and soft slashing, while major faults such as invalid blocks, double voting, or conflicting blocks can trigger hard slashing.

Then I reached transactions. Dusk uses two models: Moonlight, an account-based model with public keys, and Phoenix, a UTXO-based model using ZK proofs for privacy. The contrast is clear, but I’m still wondering how these two models affect long-term decentralization and governance in practice.

How do you view the trade-off between voter credits, penalties, and decentralization?

@Dusk #dusk $DUSK

I went back through the TermMax Token Whitepaper last night, Version 1.0 from March 2026, and I tried to understand the token design before forming any opinion.

My first takeaway is that TermMax is built as a decentralized fixed-rate borrowing and lending protocol, aiming to make DeFi interest rates more predictable through tokenization and automated market maker (AMM) technology.

The reason for that focus also became clearer. The whitepaper points out that variable rates create uncertainty for both borrowers and lenders, while predictable rates matter for capital deployment strategies used by traditional institutions and professional traders.

Then I looked at TMX itself. The total supply is exactly 1,000,000,000 TMX, fixed with no inflation. The token uses ERC20 with OFT support across multiple blockchains. The TGE date is To Be Announced, and approximately 20% of supply is expected to circulate at TGE.

TMX’s stated core functions are protocol governance, staking rewards, and ecosystem incentives. That is where I started asking more questions.

How will governance power actually be distributed? Does the fixed supply meaningfully help decentralization, or could ownership still become concentrated? And from a security perspective, how does the AMM maintain reliable liquidity when markets become stressed?

I’m still reading, so I see these as open questions rather than conclusions.

What would you examine next?

@TermMax #termmax

I went back through the Dusk documentation last night, and the incentive section made me slow down and read it twice.

What I first understood as a simple validator reward is more nuanced. Block rewards come from newly minted DUSK and transaction fees, with 80% going to the block generator, 10% to the voting committee, and 10% to Dusk. The generator’s 80% is split into a fixed 70% and a variable 10%, where the variable part depends on votes included in the block certificate. Voter rewards are based on credits, so voting power and incentives are closely connected.

That raised a question for me: does rewarding higher-credit voters strengthen participation, or could it gradually concentrate influence among already-strong provisioners?

The security side is also interesting. Minor faults can lead to suspension and soft slashing, while major faults such as invalid blocks, double voting, or conflicting blocks can trigger hard slashing.

Then I reached transactions. Dusk uses two models: Moonlight, an account-based model with public keys, and Phoenix, a UTXO-based model using ZK proofs for privacy. The contrast is clear, but I’m still wondering how these two models affect long-term decentralization and governance in practice.

How do you view the trade-off between voter credits, penalties, and decentralization?

@Dusk #dusk $DUSK

I went back through the Dusk documentation last night, and the incentive section made me slow down and read it twice.

What I first understood as a simple validator reward is more nuanced. Block rewards come from newly minted DUSK and transaction fees, with 80% going to the block generator, 10% to the voting committee, and 10% to Dusk. The generator’s 80% is split into a fixed 70% and a variable 10%, where the variable part depends on votes included in the block certificate. Voter rewards are based on credits, so voting power and incentives are closely connected.

That raised a question for me: does rewarding higher-credit voters strengthen participation, or could it gradually concentrate influence among already-strong provisioners?

The security side is also interesting. Minor faults can lead to suspension and soft slashing, while major faults such as invalid blocks, double voting, or conflicting blocks can trigger hard slashing.

Then I reached transactions. Dusk uses two models: Moonlight, an account-based model with public keys, and Phoenix, a UTXO-based model using ZK proofs for privacy. The contrast is clear, but I’m still wondering how these two models affect long-term decentralization and governance in practice.

How do you view the trade-off between voter credits, penalties, and decentralization?

@Dusk #dusk $DUSK

I went back through the TermMax Token Whitepaper last night, Version 1.0 from March 2026, and I tried to understand the token design before forming any opinion.

My first takeaway is that TermMax is built as a decentralized fixed-rate borrowing and lending protocol, aiming to make DeFi interest rates more predictable through tokenization and automated market maker (AMM) technology.

The reason for that focus also became clearer. The whitepaper points out that variable rates create uncertainty for both borrowers and lenders, while predictable rates matter for capital deployment strategies used by traditional institutions and professional traders.

Then I looked at TMX itself. The total supply is exactly 1,000,000,000 TMX, fixed with no inflation. The token uses ERC20 with OFT support across multiple blockchains. The TGE date is To Be Announced, and approximately 20% of supply is expected to circulate at TGE.

TMX’s stated core functions are protocol governance, staking rewards, and ecosystem incentives. That is where I started asking more questions.

How will governance power actually be distributed? Does the fixed supply meaningfully help decentralization, or could ownership still become concentrated? And from a security perspective, how does the AMM maintain reliable liquidity when markets become stressed?

I’m still reading, so I see these as open questions rather than conclusions.

What would you examine next?

@TermMax #termmax