Nebula
  • 👉Nebula Testnet
    • Join Nebula Protocol Testnet
    • Testing Nebula Protocol
      • Supply
      • Withdraw
      • Borrowing
      • Repay
  • 👉Nebula Overview
    • Nebula Intro
      • What is Nebula ?
      • The problem
    • Competitive Advantages
      • Innovative Collateralization with DEX LP Tokens
      • Cross-Chain
      • Yield Tranching Mechanism
      • Lending Pools
      • Consensus and Oracle
      • Smart Contract
      • Decentralized Governance
      • Community-Driven Governance
    • Comparison with Competitors (Expanded)
  • ⭐Product Feature
    • User Roles
      • Suppliers
      • Borrowers
      • Governance Participants
      • Developers
    • Protocol Architecture
      • Core Components
      • EVM Compatibility with Enhanced Security
      • Cross-Chain Interoperability via Nibiru’s IBC
      • Advanced Oracle Integration
      • Security and Scalability
        • Security
    • Nebula Product
      • DEX LP Tokens as Collateral
      • Customizable Pool Creation
      • Enhanced Liquidity
      • Cross-Chain CDP Contracts
      • Yield Tranching
    • Use Cases
  • ⭐Tech Overview
    • Nebula Technology Overview
      • Validator-Based Oracle System
      • Consensus and Voting Mechanism
      • Risk Management and Security
        • Collateralization Requirements
        • Liquidation Mechanisms
        • Insurance Fund
        • Decentralized Oracles
        • Interest Rate Risk
        • Smart Contract Security
        • Market Risk
        • Governance Risk
        • Cross-Chain Risks
      • Rewards and Slashing Mechanism
      • Scalable and Resilient Design
      • Interest Rate Model
        • Types of Interest Rates
        • Interest Rate Adjustments
        • Benefits of the Model
        • Example Scenarios
        • Governance Control
        • Competitive Advantage
      • Governance
        • Governance Framework
        • Governance Token Utility
        • Governance Process
        • Key Governance Parameters
        • Governance Security
        • Governance Use Cases
        • Long-Term Decentralization
  • Token
    • Tokenomics
      • Token Utility
      • Revenue Model
      • Supply Dynamics
      • Incentive Alignment
    • Nebula Token Info
      • Token Utility
      • Token Distribution
  • GTM
    • Roadmap
    • Points System
    • Ambassador Program(TBD)
  • Appendix
Powered by GitBook
On this page
  • 1. Glossary of Terms
  • 2. Token Allocation
  • 3. Key Technical Details
  • 4. Frequently Asked Questions (FAQs)
  • 5. References and Resources
  • Next Steps

Appendix

This appendix provides additional details to support the Nebula Lending Protocol's whitepaper, offering clarity on technical terms, token allocation, and links to relevant resources.

1. Glossary of Terms

  • Collateralization Ratio: The ratio of collateral value to the borrowed amount. For example, a 150% collateralization ratio means the collateral must be worth 1.5 times the loan amount.

  • IBC (Inter-Blockchain Communication): A protocol enabling blockchains to communicate and transfer assets securely and seamlessly.

  • LST (Liquid Staking Tokens): Tokens that represent staked assets, allowing users to maintain liquidity while earning staking rewards.

  • DAO (Decentralized Autonomous Organization): A governance structure where decisions are made collectively by token holders.

  • Smart Contract: Self-executing programs on a blockchain that automate predefined actions when conditions are met.


2. Token Allocation

Category

Percentage

Details

Liquidity Mining

40%

Rewards for liquidity providers to bootstrap liquidity pools.

Development Fund

20%

Reserved for protocol development, upgrades, and audits.

Community Incentives

20%

Allocated for partnerships, marketing, and ecosystem growth.

Team and Advisors

10%

Vested over four years to align long-term incentives.

Treasury Reserve

10%

For unforeseen expenses and future initiatives.


3. Key Technical Details

Smart Contract Repositories

  • Lending Pool Contracts: [GitHub Link Placeholder]

  • Governance Contracts: [GitHub Link Placeholder]

  • Oracle Integration: [GitHub Link Placeholder]

Cross-Chain Infrastructure

  • IBC Protocol Documentation: [Link Placeholder]

  • Supported Blockchain Networks: Ethereum, Cosmos, Nibiru.

Auditing Reports

  • Audit Report 1 (Firm Name): [Link Placeholder]

  • Audit Report 2 (Firm Name): [Link Placeholder]


4. Frequently Asked Questions (FAQs)

  • What assets can I use as collateral? Initially supported assets include USDT, USDC, ETH, and native Nibiru tokens. The community can vote to add more assets through governance.

  • How are interest rates determined? Interest rates adjust dynamically based on the utilization ratio of each liquidity pool. A stable rate option is also available for predictable borrowing costs.

  • What happens if my collateral value drops? If the collateralization ratio falls below the required threshold, a portion of your collateral will be liquidated to maintain the protocol's stability.

  • How do I participate in governance? Stake Nebula tokens to gain voting power and participate in on-chain governance proposals.

  • Is Nebula interoperable with other blockchains? Yes, Nebula leverages the IBC protocol to support cross-chain lending and borrowing.


5. References and Resources

Nibiru Blockchain Documentation

  • [Nibiru Documentation Link]

DeFi Protocol References

  • Aave Whitepaper: [Link Placeholder]

  • Compound Documentation: [Link Placeholder]

Community and Support

  • Discord: [Link Placeholder]

  • Twitter: [Link Placeholder]

  • Medium Blog: [Link Placeholder]


Next Steps

This appendix serves as a supplementary resource for understanding the Nebula Lending Protocol and its ecosystem. For further inquiries, users and developers are encouraged to engage with the Nebula community or explore the resources provided.


How to Include in GitBook:

  1. Create a Chapter: Add a new chapter titled "Appendix" in the table of contents.

  2. Subsections: Use headers (## or ###) to break the content into manageable parts like "Glossary of Terms," "Token Allocation," etc.

  3. Links and Placeholders: Replace placeholders with actual links to relevant resources (GitHub repositories, audit reports, community pages).

  4. Styling: Use tables for structured data like token allocation and FAQs for clarity.

This structure ensures that the appendix is user-friendly and easy to navigate within your GitBook documentation.

PreviousAmbassador Program(TBD)

Last updated 5 months ago