Mission
To build smart contracts that enforce what others merely promise — open, verifiable systems whose rules are code that anyone can read, run, and check.
Smart Pacts
Smart Contracts, Smarter Solutions
Smart Pacts is a smart contract development company. We design, build, audit, and operate on-chain systems on the Kadena network — contracts that enforce what others merely promise, published in full and verifiable by anyone.
See everything, liveYour SPTRead the contracts ↗
The SPT token contract is deployed on Kadena mainnet on all 20 chains, and the sale contract on chain 0. The full source is published, and the code running on chain is byte-for-byte the code in the public repository — anyone can check that without trusting us.
> (describe-module "n_4886…e3.SPT")
→ the exact source and its hash
→ verifiable by anyone — free, no account20chains, one deployment
100,000fixed supply — created once
2open-source modules
0mint functions
Who we are
Vision
A digital economy where agreements don't depend on trust in intermediaries: every important promise is a public contract, every rule is enforced by the network that hosts it, and anyone can verify everything.
What we do
On-chain products
We build and operate our own systems end to end. SPT — a fixed-supply token with advisory governance and holder-claimed distributions that the administrator declares and funds on chain — is live on Kadena mainnet. The Gallery, an NFT marketplace whose contract pays the creator’s royalty on every sale it settles, runs on a public test network.
Smart contract development
We work in Pact on the Kadena network: architecture, implementation, testing, and security review of contracts built to hold up under adversarial eyes — and we publish the tests alongside the code.
Verification as a habit
Everything we deploy is open source and verifiable against the chain — the code the chain returns can be compared byte-for-byte with the published deploy bytes — with runnable conformance suites. You should not have to trust us — and with our work, you don’t have to.
What is live
Three pages, one contract. Each of these talks to Kadena mainnet directly from your browser.
Transparency
Where every token is, what is time-locked and until when, what funds the contract holds, and what the administrator can and cannot do — read from the chain each time the page loads. It asks nothing of you.
Your SPT
Balances across all 20 chains, transfers, moves between chains, voting and reward claims. Every action is signed in your own wallet; the site never holds a key.
Buy SPT
Tokens are bought from a reserve on chain 0, at a price recorded on chain. The sale is not open right now; the page reads that state live and says so.
How it works
Five mechanisms, all enforced by the contracts as deployed — none by policy or promises. One caveat, said once: the contract is not yet frozen, so until it is, the administrator can still upgrade it. Freezing is permanent, and the transparency page shows the current state live.
Fixed supply
100,000 SPT were created exactly once, in a single initialization transaction on chain 0 that refuses to run again — and no other function in the deployed code creates supply. A transfer between chains left half-finished holds those tokens in transit — debited on one chain, not yet credited on the other — until someone completes the second step, which anyone can do. How many can exist is answered by code, not policy.
Advisory voting, live and chain-local
Your voting weight is your current balance on the chain where your tokens live, and re-voting is always allowed. Move tokens and their weight is released from your vote in the same transaction — the same token can never be counted twice on the same proposal. Each chain records its own tally and nothing on chain adds them up: the result is the sum of all 20, and it is a result only once every chain’s record exists, has closed and agrees — anyone can read all 20 and check that. Every vote is advisory.
Distributions to holders
Funding arrives on-chain in KDA. The administrator declares each round on chain in advance, chain by chain — a rate per token against a sealed record date on that chain. Whoever held tokens on that chain at that instant accrues that rate there; tokens mid-way through a move between chains at that moment sit on no ledger and accrue nothing for that round. The treasury is excluded. Claims are permissionless and carry no deadline; whoever sends the claim pays the network fee.
Time-locked reserves
The founder, treasury, and liquidity reserves sit in key-less, contract-guarded accounts with release calendars fixed at initialization — a cliff, then linear release. Nothing can be accelerated or revoked, and there is no admin unlock. The calendar fixes when tokens can move; where they go depends on the reserve. Unlocked treasury and liquidity tokens go to whichever existing account the administrator chooses. Unlocked founder tokens can only ever go to the address fixed at initialization, and anyone can trigger that release.
Everything verifiable
The treasury, founder and liquidity reserves hold no key of their own — they are guarded by contract rules, and the ordinary transfer path refuses them outright. Vested treasury and liquidity tokens leave only through a calendar-capped disbursement that takes two of three governance devices; vested founder tokens leave only to the address fixed at initialization. The source, module hashes, balances, tallies and lock schedules are all readable on mainnet, free, without an account — and the transparency page reads them for you.
Verify it yourself
Nothing on this page asks for belief. Here is exactly what is deployed, and where:
Network
Kadena mainnetNamespace
n_48867b242317a0216a67f8c7ca26696b5878e0e3Modules
SPTSPT-launch(describe-module "n_48867b242317a0216a67f8c7ca26696b5878e0e3.SPT")That query returns the exact source running on chain — free, no account. The transparency page runs the comparison against the published source in your browser and shows the result. The full source, the test suite and the deploy bytes are published: github.com/SmartPacts/spt ↗