Uh oh!
There was an error while loading. Please reload this page.
docs: developer NFT rewards page - #439
Conversation
New guide under Frontend & SDK Integration covering how the developer NFT is minted, how it earns from the fee share and inflation share, when rewards become claimable, and how to read/claim with GenLayerJS. Uses the new getDeveloperNft / getClaimableRewardsFrom* / claimNft* actions.
✅ Deploy Preview for genlayer-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
New guide under Frontend & SDK Integration (sibling of reading-data / writing-data) covering the developer NFT reward mechanism and how to read/claim rewards with GenLayerJS.
Covers: how the NFT is minted (first deploy, one per developer), the two earning sources (fee share ~10% at finalization; inflation share, pro-rata by fees, 1× cap), when rewards become claimable, and worked GenLayerJS examples for
getDeveloperNft/getClaimableRewardsFrom*/claimNft*(from genlayer-js PR #195). Mirrors the reading-data/writing-data page conventions; adds one_meta.jsonnav entry.ghostToNFT == 0, so its fees are skipped). It sits adjacent to a fund-loss bug we just reported to the consensus team — please confirm the framing is how you want it stated publicly, or whether to soften/omit until the contract behavior is settled.getClaimableRewardsFromInflationcan report more than a singleclaimNftEpochswill pay. Accurate today, but if the SDK later adds client-side clamping this note should change.Draft — not for merge until the above are confirmed.