MemoDueCompliance
DevnetManage
Devnet only. This page reads and writes the MemoDue compliance config and note takedown flags on Solana devnet through api.devnet.solana.com. Switch Phantom to devnet first: Settings > Developer Settings > Testnet Mode on, network Solana Devnet. On a phone, open this page inside Phantom's in-app browser to sign.
Reading needs no wallet. Every transaction is simulated on devnet and decoded for review before Phantom is asked to sign. Only the compliance authority can sign compliance changes and takedowns; the fee authority has no compliance rights.
eSafety takedown
Respond within 24 hours of receiving an eSafety removal notice. Set Pending first to block reads at once, then Final or Clear after review.
On-chain data cannot be erased. A takedown sets a flag on the note: the gates refuse to release the key and this site refuses to show the note. The encrypted bytes stay on Solana until the note is closed. Old Plain notes (versions 1 to 4) have no takedown flag, and anyone holding a Plain link (key in the link) can still decrypt it with other software. Use the blocked-notes list (scripts/moderation-block.mjs) for those.
A later move of the compliance authority to the Squads vault 3upS…dAEK would mean each takedown is a Squads proposal approved by the multisig, not a Phantom signature here.
- Note
- Version
- Tier / gate
- Status
- Takedown
Compliance
On-chain blocklist. Each configured sanctions list provider owns one bit in a wallet's blocked account and sets or clears only its own. The program refuses create for a creator, and keeper close for a closer, while any enforced list flags the wallet. Rent owed to a flagged creator is frozen: every close of their notes (their own close, the unfinished-note refund and keeper closes) is refused, and the rent stays in the note account. Nothing is swept or taken. Delisting the wallet, or turning the list's enforcement off, makes closing work again at once. The compliance authority is a separate key from the fee authority: neither can use the other's powers. Needs the program upgrade; before it, this section only reads.
Open this section to load the compliance config.
- Config PDA
- Compliance authority
- Pending handover
Lists
Blocked addresses
Every blocked account of the program (one getProgramAccounts call, filtered by size and tag).
Danger zone: compliance authority
Compliance authority handover. The compliance authority adds, enforces and removes lists, runs the manual override and hands this role over. It has no fee rights, and the fee authority has no compliance rights. Changing it needs the address entered twice, a typed confirmation word and the decoded review before Phantom is asked to sign.
Only the compliance authority can propose a new compliance authority. Connect that wallet to see the form.
Accept compliance authority
This wallet has been proposed as the new compliance authority. Accepting makes it the compliance authority: it then manages the lists and the manual override and can propose the next one. The current compliance authority loses that power. Fee settings are not affected.
Pending compliance authority proposal
- Proposed
- Proposed by
- When
Nothing has changed yet. The proposed wallet must connect here and sign Accept compliance authority. The compliance authority can cancel until then.