Resources & links

This page collects external links, the partner ecosystem Milky builds on top of, and the places to reach the team.

Try the protocol

Open the app — connect a wallet and see live pools, your positions, and active auctions.
Borrow — start a loan against a card you own.
Lend — view available pools (deposits currently restricted to pool admins; see the single-LP note).
Premium auctions — browse active default auctions.

Follow Milky

Live channel for updates, support, and announcements:

X (Twitter): @milky_protocol

Partner ecosystem

Milky builds on a stack of established Solana and trading-card infrastructure providers:

Solana — the underlying blockchain.
Anchor — the Solana program framework.
Metaplex — NFT and programmable-NFT standards used by the cards Milky accepts as collateral.
Helius — RPC infrastructure powering the indexer and front-end data.
Circle — issuer of USDC, the loan currency.
Alt.xyz — primary oracle data source for graded-card pricing.
CollectorCrypt — Solana-native tokenization issuer that vaults graded cards and mints the NFTs Milky lends against. Custody of the physical cards remains with the issuer.
Phygitals — second tokenization issuer whose minted NFTs are recognized by Milky, with the same custody model as CollectorCrypt.
Colosseum — Solana hackathon and ecosystem incubator.

Found a mistake, an outdated number, or a section that's unclear? Reach out on X (link above). The documentation reflects the deployed protocol; if the doc and the deployed program ever disagree, the program wins — and we want to know about it.

For developers

Public technical resources will live alongside the production launch:

Program ID: to be published once the production deployment is finalized.
GitHub: open-source releases will be tagged on the official repo once published.
SDK: TypeScript client packages are part of the public release plan.

In the meantime, the on-chain program is publicly inspectable on Solana via any block explorer once you have its program ID.

Security disclosure

Security findings should be reported through the official channel (see X above). The protocol team treats security disclosures with priority, and a formal responsible-disclosure policy is part of the production launch documentation.