Kyoko
  • Kyoko Introduction
  • HOW IT WORKS
    • Peer-to-Pool NFT Lending Platform
      • P2P NFT Lending Introduction
        • As Lenders: Earning Interest
        • As Borrowers: Get Instant Loans
        • NFT as the collateral
        • NFT Price Discovery
      • Who can create the pools?
        • The Blue-Chip Pools
        • The Shared Pool
      • Risk Models: Health factor or Time-based
        • Risk Framework
        • Dual Rates
        • NFT Risk Parameters
      • Pending Liquidation
        • Auction liquidation
        • Bad Debt
      • Security and Audits
    • Cross-Chain GameFi Assets Lending(CCAL)
      • How to use Cross-Chain GameFi Assets Lending?
      • FAQ for CCAL
  • TOKEN
    • Token distribution
    • Understanding $KYOKO in P2P NFT Lending
      • Staking (Shared income)
        • Staking your $KYOKO
        • Claiming shared income
      • Voting
        • Vote Locking
        • Governance Mechanism
        • Snapshot
        • Proposals
    • Vesting
    • Stake
      • Liquidity Mining
      • How to start staking?
    • Business Model
    • Governance
      • KRCs
      • KIPs
      • Governance forum
      • Voting(Snapshot)
  • Roadmap
  • Security and auditing
  • Contact
  • DEPLOYED CONTRACTS
    • P2P NFT Lending
    • Cross-Chain GameFi Assets Lending(CCAL)
  • TEST
    • P2P NFT Lending testnet
    • Cross-Chain GameFi Assets Lending(CCAL)
  • COMMUNITY
    • Twitter
    • Telegram
    • Discord
    • Medium
    • Github
    • TERMS OF SERVICE
Powered by GitBook
On this page

Was this helpful?

  1. DEPLOYED CONTRACTS

P2P NFT Lending

PreviousContactNextCross-Chain GameFi Assets Lending(CCAL)

Last updated 3 years ago

Was this helpful?

The P2P NFT Lending protocol is one of the Kyoko products that aims to provide the solution for NFTs liquidity.

The following contracts are released on the Ethereum:

Contracts
Code
Address

LenderToken

KyokoP2P

Configuration

At present, all permissions are took over by the multi-signature management to ensure the protection from hacker attacks.

Multi-Sign Address: 0x87ee0Ff5628cDA2F03120B6F727699021A52a842

Github
0xB9f42598cbaF93B023cbBE87CD636e77B6cE68B8
Github
0x15e904D6d9188FA0ED26D419D4df74F131D798a3
Github
0x4e24596a6484f5b45Cf4C7708F6f652Ee034b235