Most chains make token creation a developer task. Write a contract. Set up a toolchain. Deploy to a testnet. Debug. Redeploy. Pay gas. Pray the indexer picks it up.
On Ethereum, deploying an ERC-20 costs between $50 and $500 in gas depending on the day. On Solana, you need a Rust toolchain. On BSC you are still writing Solidity and managing your own deployment pipeline.
Magi just collapsed that entire process into two wallet prompts and 10 HBD.
The vsc-eco/token-sdk repository, now public on GitHub, is a complete token issuance and management toolkit for the Magi network. Three packages. MIT licensed. Zero backend requirements.
@vsc.eco/token-core — operation builders and types. Zero dependencies.
@vsc.eco/token-sdk — Hasura-indexed reads for balances, collections, token supply, ownership. Built-in failover across multiple indexer mirrors. If one node goes down, the SDK silently routes to the next.
@vsc.eco/token-widget — drop-in React and web components. <MagiNftPanel>, <MagiTokenPanel>, <MagiAssets>. One tag gives your users a full asset management interface: transfer, burn, batch transfer, mint, deploy. Dark and light themes. Embeddable in Keychain, Peakd, Ecency, or any app that touches Hive.
The SDK talks to deploy.okinoko.io — the infrastructure layer that handles contract compilation and deployment orchestration. Click Deploy in the widget and here is what happens:
The SDK sends the request to the okinoko deployer. The backend clones the contract repo and compiles the WASM. Build logs stream back in real time.
When the build succeeds, the backend returns the exact Hive operations to sign. The user signs once via Aioha — Keychain, HiveSigner, HiveAuth, PeakVault, Ledger, whatever they have.
The SDK polls the Magi indexer for the new contract ID, then fires the init() call with the name, symbol, and metadata from the form. Second wallet prompt. Done.
Two signatures. One fee. A fully initialized contract on Magi with the contract ID ready to use.
Magi Token — fungible tokens with configurable decimals. Full transfer, transferFrom, approve, allowance management. Owner can mint, burn, pause, transfer ownership.
Magi NFT — multi-token collections with per-token properties, soulbound tokens, editioned mints, series templates, collection-level metadata. Transfer, batch transfer, burn, batch burn, approve, setApprovalForAll.
deploy.okinoko.io — contract deployer backend. Compiles WASM, orchestrates deploys, streams build logs.
api.okinoko.io — one of multiple indexer mirrors alongside indexer.magi.milohpr.com, api.vsc.eco, and vsc.techcoderx.com. Automatic failover.
terminal.okinoko.io — the main Magi dashboard. The Token SDK was extracted from this codebase. Same operation formats, same image resolution logic, unbundled and made embeddable.
<MagiAssets>, one component, NFTs and tokens tabbed, wallet search, deploy button, refresh, theming.<magi-assets>, <magi-token-panel>. Works in vanilla JS, Vue, Svelte. No React required.onBroadcast instead of Aioha. You sign however your app already does.The SDK also handles Hive's ~5 custom_json per block cap automatically. broadcastBatch chunks operations, sleeps between blocks, exposes progress callbacks. Airdrops to 200 holders just work.
Here is the part that makes all of this bigger than a token factory.
Magi nodes runs a DID-based account system. Every wallet address from every supported chain is a first-class account in the same ledger. Not through a bridge. At the consensus layer.
EVM - MetaMask, Coinbase Wallet, Rainbow, Trust Wallet, and hundreds of others via WalletConnect v2.
Bitcoin - BIP-137 and BIP-322 message signatures. P2PKH, P2SH. Xverse, Leather, and any wallet that can sign a message.
Hive — eight Aioha providers. Keychain, HiveAuth, HiveSigner, Ledger, PeakVault, MetaMask Snap.
And beyond wallets entirely (coming soon): passkey-derived accounts — Google Sign-In to a deterministic cryptographic key. No wallet app. No browser extension.
The Magi ledger stores hive:lordbutterfly, did:pkh:eip155:1:0xABC..., and did:pkh:bip122:...:bc1q... as keys in the same balance database. A Hive user can send tokens to an Ethereum address. An Ethereum user can transfer an NFT to a Bitcoin address. The contracts do not care which chain the signature came from. They check msg.caller, and the node resolves that to whatever DID signed the transaction.
The Token SDK's widget layer currently targets Hive wallets, that is what is live today. Multi-chain widget support, where EVM and Bitcoin wallets interact with tokens and NFTs directly through the embeddable panels, is the next phase. The hard part is already done: node-level signature verification, DID-native ledger, chain-agnostic contract execution. The remaining work is SDK wiring, not architecture.
This is all coming together.
Every L2 in crypto locks you into one community. Build on Arbitrum, your market is Arbitrum users. Build on Optimism, Optimism users. Want Bitcoin holders? Build a bridge. Want Hive communities? There is no path.
Magi is building toward something different. One deploy. One contract. Accessible to Hive users today, and to Ethereum, Bitcoin, and passkey users as the SDK catches up to what the backend already supports. The architecture does not need to change. The contracts do not need to change. The multi-chain foundation is already underneath everything the Token SDK ships today.
The rest of DeFi builds tokens for one community at a time. Magi is building the infrastructure to serve all of them at once.
https://peakd.com/me/proposals/378