Feat/btc summer integration #304
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Updated main description from 'Consumer Chain' to 'fully sovereign Cosmos chain' - Removed references to Interchain Security (ICS) dependency - Updated architecture description to reflect sovereign chain design - Aligned with Neutron's current status as independent sovereign chain
- Updated favicon to match new branding/design - Improved visual identity across documentation platform
- Add prominent 'are now live' notification with direct app links - Move how-to deposit section higher for better visibility - Add step-by-step deposit guide with visual card layout - Include current live pairs and deposit caps table - Improve Mermaid diagram colors for dark mode readability - Fix link styling for better visibility in light mode - Add internal navigation between sections Related to comprehensive docs update in PR #300
- Remove deploy.yml workflow that was failing due to missing yarn.lock - Repository uses Mintlify for deployment, not GitHub Pages - This fixes the deployment error and allows Mintlify to work properly
- Remove check-build.yml that tries to use yarn commands - Mintlify handles builds automatically, no need for manual build checks - Keep pr.yml for Telegram notifications only
- Add small change to trigger fresh content indexing - Supervaults updates should be included in this deployment
- Remove redundant 'underline decoration-primary/50' classes - Keep hover:underline for interactive feedback - Maintain font-bold for 'are now live' emphasis
- Updated DEX reference with latest changes - Part of ongoing documentation improvements for live deployment
- Link to operators/running-a-node#system-requirements for detailed info - Maintain quick reference specs while avoiding redundancy - Improve navigation between related documentation sections
- Create new BTC Summer section in navigation - Add btc-summer/overview.mdx with campaign rationale - Explain Leverage Looping and Basis Trading strategies - Link to existing Supervaults documentation - Highlight Neutron's unique DeFi infrastructure advantages
- Fix dollar sign math formatting issue with escaped characters - Remove Note wrapper from final statement for cleaner presentation - Update section heading from 'Problem' to 'The Problem'
- Apply user modifications to content structure and formatting
- Add btc-summer/overview.mdx with campaign overview and market context - Add btc-summer/campaign.mdx with detailed campaign mechanics, points system, and participation paths - Add btc-summer/vaults.mdx with technical vault behavior and deposit/withdrawal flows - Add btc-summer/technical.mdx with complete technical implementation details - Update docs.json to include BTC Summer section in navigation - Update supervaults.mdx to reflect live status with actionable steps - Add epoch.png image for campaign timeline visualization - Convert step-by-step guides to use Mintlify Steps component - Optimize content for external audience while maintaining technical accuracy
…on SubDAO and simplify governance-based management section
…on SubDAO and simplify governance-based management section
- Restore btc-summer/campaign.mdx with detailed campaign mechanics and points system - Restore btc-summer/technical.mdx with complete technical implementation details - Files were lost during PR merge, recovered from commit 5a91822
…ocs.json - Add btc-summer/campaign and btc-summer/technical to navigation - Now fully aligned with PR #304 structure - All four BTC Summer pages now accessible in documentation
- Create comprehensive btc-summer/rewards.mdx covering reward mechanisms - Explain base rewards calculation and points system - Detail NTRN locking boost with formula and benefits - Cover NFT collection boosts with tier structure - Explain wallet linking for cross-chain deposits - Include multiplier stacking and optimization strategies - Add rewards page to BTC Summer navigation in docs.json
- Update overview.mdx: Fix problem statement, add strategic emphasis, correct dollar formatting - Update campaign.mdx: Add reward distribution model, soft-lock mechanics, fix terminology - Update vaults.mdx: Correct numbering, fix USDC vault spec, improve descriptions - Update rewards.mdx: Ensure 100% accuracy with source specs for NTRN locking and NFT boosts - Update address-linking.mdx: Add professional table formatting, complete technical accuracy - Update reference.mdx: Perfect alignment with contract addresses and token denominations - All pages now 100% accurate to source documents and appropriate for external audience
- Resolved conflicts in campaign.mdx and docs.json - All BTC Summer documentation now 100% accurate to source documents - Complete page set: overview, campaign, vaults, rewards, technical, address-linking, reference
- Fixed parsing error at line 28 caused by git merge conflict markers - Resolved all <<<<<<< ======= >>>>>>> markers throughout the file - Campaign.mdx now loads properly without parsing errors
- Added 6-card overview section with icons and descriptions for each vault type - Added HTML anchor tags to section headings for reliable navigation - Fixed all card href links to properly navigate to respective sections - Cards provide quick access to: Structured KYC, LST wBTC pairs, wBTC vaults, wBTC Just Lend, LST maxBTC pairs, and USDC-MaxBTC vault
swelf19
reviewed
Aug 28, 2025
| ### Core Components | ||
|
|
||
| **Boost Pointer Contract** | ||
| - Simple staking contract accepting NFT deposits |
There was a problem hiding this comment.
The same contract accepts both NFT and NTRN deposits.
NTRN deposits are locked for a user-specified period,
NFT deposits are not locked.
| - Maps boost sources to target deposit addresses | ||
|
|
||
| **Lock Receipt NFTs** | ||
| - Functional NFTs representing locked NTRN positions |
There was a problem hiding this comment.
And again. accept reresents both, nft and ntrn
NFT representing NFT
"32997076-neutron1ex803g86qrlt5r78s2cpca0g93wpkrh0fp6ufw-galactic-quark-#4386",
{
"owner": "neutron1ex803g86qrlt5r78s2cpca0g93wpkrh0fp6ufw",
"approvals": [],
"token_uri": null,
"extension": {
"superbolt": {
"superbolt_contract": "neutron1xhjf62ezn23ugvyp4t73gusrarwhha8sk5wrc5vut4tsr4ks7fvqsyquch",
"superbolt_token_id": "galactic-quark-#4386",
"boost_for": "neutron1ex803g86qrlt5r78s2cpca0g93wpkrh0fp6ufw"
}
}
}
NTRN
"33386893-neutron1ex803g86qrlt5r78s2cpca0g93wpkrh0fp6ufw-186400-9",
{
"owner": "neutron1ex803g86qrlt5r78s2cpca0g93wpkrh0fp6ufw",
"approvals": [],
"token_uri": null,
"extension": {
"dntrn": {
"dntrn_locked": "9",
"create_date": 1756290140,
"unlock_date": 1756476540,
"boost_for": "0x766571facc16b3cfe8a109cac461ab3a3344e1d4"
}
}
}
| - Functional NFTs representing locked NTRN positions | ||
| - Store lock duration and amount information | ||
| - Transferable on secondary markets (Superbolt) | ||
| - Must be staked to Pointer Contract to activate boost |
There was a problem hiding this comment.
https://www.notion.so/hadron/Points-backend-and-contracts-20785d6b9b108064abeae97e2ebb3d1e?source=copy_link#25585d6b9b1080eea588f71a43bec65a
Boost flow section may help you. But in two words
- user sends and locks NTRN to boost pointer contract, gets bonus NFT (locked NTRN)
- user sends (no locking) superbolt to same boost pointer contract, gets bonus NFT (superbolt NFT)
No need to stake NTRN-NFT second time
| 3. **Address Recovery**: Contract uses `ecrecover` to verify Ethereum address | ||
| 4. **One-Time Signatures**: Implement sequence numbers to prevent replay attacks | ||
|
|
||
| ### Boost Transfer Mechanics |
There was a problem hiding this comment.
From a technical perspective, it works a bit differently.
A boost NFT has a boost_for field - the address recorded in this field receives the bonus. It may not match the NFT owner’s address. When the NFT is transferred, this field remains unchanged. To update the field, the NFT holder must call the update_boost_for method on the NFT boost contract.
But from the UI standpoint, we can implement transfer + update_boost_for within a single transaction.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.