"Non-custodial" gets said a lot in crypto. Here's exactly what makes it true for MACCARDANO, not just claimed.
Our backend only ever sees public key hashes - 28-byte digests. You cannot reverse a key hash back into a private key. It's a one-way function.
Every unsigned transaction is built entirely from public blockchain data: UTxOs, slot numbers, script hashes. No secret is required to build it.
The only secret that ever exists is your signing key. It's generated and stored in your wallet or hardware device. It never touches our servers. Not once.
@CheekyCrypto There's a middle option for ADA: self-custody without one key being a single point of failure. In a native script 2 of 3 wallet you hold your own keys, losing one doesn't lock you out, and no single stolen key can move funds. You can set it up here: https://t.co/abqGBUeyhR
@Lucasdb86@IOGroup Good question to keep asking. When a multisig committee fails, it's usually because the signers weren't truly independent: same team, same servers, same bad day. The signer count matters, but so does who holds each key and where.
@jasonappleton Repayment plans would need somewhere checkable for the funds to sit. If supported projects held treasury ADA in a native script N of M wallet with independent signers, DReps could follow every payment, and every repayment, on chain.
Cardano native scripts can express three kinds of signing rules:
All: every listed key must sign
Any: one key is enough
At least N of M: for example 3 of 5
No smart contract, just rules Cardano checks itself. For shared ADA, N of M is the usual pick:
https://t.co/abqGBUe0sj
@JaromirTesar Capped domains with named stewards make sense. One thing worth writing into each mandate: where the domain's ADA sits and how many independent signers must approve each payment. A native script N of M wallet makes that checkable on chain by anyone.
One wallet, three ways to sign.
Co-signers on a MacCardano multi-sig can approve proposals on the website, from the CLI tool on Linux or Windows, or by tapping a Tangem card in our Android companion app (iOS in progress).
Same native script, same on-chain rules:
https://t.co/cljIe4OtGB
Cardano Foundation's DRep voted NO on the 22M ADA copper proposal, partly because the funds would sit under a single party's control.
Simple test for any shared ADA: how many keys can move it alone?
If the answer is one, an N of M native script wallet changes that:
https://t.co/cljIe4OtGB
@RanterSR7 Good list. One Cardano bonus for the mom test: native multi-sig. A 2 of 3 family wallet, where she holds one key and two trusted people hold the others, means one lost key isn't the end and no single key can move it. You can set it up here: https://t.co/abqGBUeyhR
@Varavas9 Good follow-up. The useful part on Cardano: you don't have to take anyone's word for it. Once funds move from a native script address, its rules are in the transaction, so anyone can check how many signatures it requires.
What happens to a multi-sig proposal that doesn't get enough signatures?
Nothing. It never executes, and the ADA stays exactly where it is.
In a native script wallet, Cardano itself checks the threshold, not us. No admin can push a payment through:
https://t.co/abqGBUe0sj
@MikeCChandler Agreed. For anything shared or larger, self-custody can go one step further: split control across several keys in a native script multi-sig, so one lost or stolen key can't move the ADA.
Clear milestones and budgets are a great start. One thing DReps increasingly ask about is custody: where the ADA sits and how many independent signers approve each payment. A native script N of M wallet makes that verifiable on chain. You can set it up here: https://t.co/cljIe4OtGB
@RatifyWeekly Thanks! It's the question we'd ask of any shared wallet, treasury or team. If the answer is one, that's the risk, whatever else is in place.
Preparing a 2027 Cardano treasury proposal?
Beyond milestones and budgets, say where the ADA will sit once paid out and how many independent signers must approve each payment.
A native script N of M wallet makes that checkable on chain:
https://t.co/abqGBUeyhR
@CheekyCrypto For us, yes. The concern was one party controlling 22M ADA. Spreading control across several independent signers in a native script wallet, with every payment visible on chain, is exactly the kind of safeguard that answers it.
@MikeCChandler Solid list. We'd add a sixth: where does the ADA sit once it's paid out? In a native script N of M wallet, no single person can move it and every payment can be checked on chain. Check it out here: https://t.co/abqGBUe0sj
What if our website went offline tomorrow?
Your funds would be fine. The wallet is a native script on Cardano, proposals and signatures are stored on chain, and our site stores nothing.
For that day, there's a CLI recovery tool for Linux and Windows. Your keys, your chain:
https://t.co/cljIe4OtGB
@CardanoRecord Moments like this are where on chain controls help. When program funds sit in a native script N of M wallet, every release needs several independent signatures and every payment is visible to DReps. Check it out here: https://t.co/abqGBUeyhR
@CheekyCrypto Custody proof matters after the ADA leaves too. One step any funded team can take: hold the withdrawn ADA in a native script N of M wallet with independent signers, so every payment is a signed proposal DReps can check on chain. You can set it up here: https://t.co/abqGBUeyhR