DOXA SNS Proposal 143605: Unanswered U.S. Participation and Compliance Questions

DOXA SNS Proposal 143605: Unanswered U.S. Participation and Compliance Questions

I reviewed the original DOXA SNS discussion and the later swap thread.

Community members already raised legitimate questions about:

  • Why DoxaUSD is needed instead of using ckUSDC directly
  • The source and sustainability of the proposed yield
  • The precise nature of the claimed Paxos relationship
  • The still-developing Ondo integration
  • Team identities
  • Open-source code, canister IDs, and reproducible builds

Some of those questions received partial answers. However, I found no on-record response addressing U.S. participant eligibility or the legal treatment of either DoxaUSD or the DOXA governance token in the United States.

That issue deserves an answer before people located in the United States contribute ICP.

Why this matters

The published SNS configuration does not include the United States among its restricted countries. It also leaves the optional participant confirmation and risk-warning text commented out.

Meanwhile, the DOXA whitepaper describes DoxaUSD as:

  • A U.S.-dollar-pegged stablecoin backed 1:1 by ckUSDC
  • Mintable and redeemable through DOXA canisters
  • Intended for payments, savings, payroll, remittances, and merchant settlement
  • Available for staking or locking to earn yield
  • Eventually backed partly by tokenized U.S. Treasury products
  • Designed to distribute DoxaUSD staking rewards in DOXA tokens

The proposal materials also state that ICP staking rewards and future Treasury-derived revenue will fund DUSD staker yields and support DOXA token value accrual.

These are financial-product representations, not merely technical features.

Important legal distinction

The SNS swap distributes the DOXA governance token, not DoxaUSD itself. Therefore, the GENIUS Act does not automatically establish that Americans must be excluded from the SNS swap.

However, that does not establish that U.S. participation is lawful either.

There are at least two separate legal questions:

  1. Whether DOXA tokens may be offered through the SNS swap to persons located in the United States.
  2. Whether DoxaUSD may be issued, offered, redeemed, staked, or otherwise made available to U.S. users.

Both require an affirmative legal basis. Neither appears to have been documented publicly.

The GENIUS Act

The United States enacted the GENIUS Act, Public Law 119-27 on July 18, 2025.

The Act takes effect no later than January 18, 2027, or 120 days after final implementing regulations are issued if that occurs earlier. Treasury published a new proposed implementation rule on August 18, 2026, with comments due October 19, 2026.

Among other things, the statutory framework addresses:

  • Who may issue a payment stablecoin in the United States
  • Foreign stablecoin issuers serving U.S. users
  • One-to-one eligible reserves
  • Public redemption policies
  • Monthly reserve reporting and examination
  • Bank Secrecy Act and sanctions compliance
  • The technological ability to comply with lawful freeze, seizure, or transfer-prevention orders
  • Restrictions on paying interest or yield solely for holding, using, or retaining a payment stablecoin

The Act also has extraterritorial provisions when payment stablecoins are offered or sold to people located in the United States.

Because the DOXA roadmap extends into 2027 and beyond, this cannot reasonably be dismissed as a distant issue.

Questions the DOXA team should answer on the record

1. Who is legally issuing DoxaUSD?

What existing legal entity is responsible for minting DUSD and honoring redemption?

The whitepaper identifies the DOXA Foundation but says it may later be reincorporated in the Cayman Islands, Switzerland, or Wyoming. That does not identify the present issuer’s jurisdiction, regulatory status, assets, or legally enforceable obligations to token holders.

Please provide:

  • The issuer’s full legal name
  • Its current jurisdiction and registration
  • Its regulator or licensing authority, if any
  • The entity legally obligated to redeem DUSD
  • The entity that owns or controls the reserve assets

2. What is DoxaUSD’s legal classification?

Does qualified U.S. counsel consider DUSD a “payment stablecoin” under the GENIUS Act?

The statute’s definition refers to an issuer obligated to redeem a token for a fixed amount of monetary value. DUSD appears to be collateralized and potentially redeemable using ckUSDC, which is itself a digital asset.

If DOXA believes DUSD falls outside the GENIUS Act’s definition, what legal category does it fall under, and which laws govern its issuance to U.S. users?

If it falls inside the definition, what is the plan to become:

  • A permitted U.S. payment-stablecoin issuer, or
  • A qualifying and registered foreign payment-stablecoin issuer?

3. What authorizes U.S. participation in the DOXA token sale?

Has qualified U.S. counsel analyzed the DOXA SNS decentralization swap under federal and state securities laws?

The project’s materials discuss protocol profits, investor benefits, DOXA buybacks or purchases, increased demand, and long-term token value accrual. That does not automatically make DOXA a security, but it makes a documented legal analysis necessary before the token is offered to U.S. participants.

Please identify any registration, exemption, exclusion, or other legal basis being relied upon.

4. Is ckUSDC an eligible reserve for DoxaUSD?

The fact that ckUSDC represents bridged USDC does not by itself answer whether holding ckUSDC as collateral for a second stablecoin satisfies the GENIUS Act’s reserve requirements.

Please explain:

  • Whether the legal analysis looks through ckUSDC to USDC’s underlying reserves
  • Whether DUSD holders have a direct or indirect redemption claim
  • Whether one DUSD is redeemable for one U.S. dollar, one USDC, or one ckUSDC
  • Redemption fees, limits, delays, and suspension rights
  • What happens if ckUSDC, USDC, a canister, or a bridge mechanism fails

On-chain visibility proves what a canister holds. It does not by itself establish that the reserve structure is legally eligible or that users possess enforceable redemption rights.

5. How will the DUSD yield comply?

The whitepaper says users can stake or lock DUSD and earn rewards paid in DOXA.

The GENIUS Act prohibits permitted and foreign payment-stablecoin issuers from paying yield—including yield paid in tokens—solely in connection with holding, using, or retaining a payment stablecoin.

What legal structure allows DOXA to pay DOXA tokens to DUSD stakers without violating that restriction once it becomes applicable?

This should be answered by qualified counsel, not merely described as “protocol yield.”

6. How will AML, sanctions, and lawful orders be handled?

The whitepaper repeatedly describes DUSD as permissionless and censorship-resistant. The U.S. framework, particularly for foreign issuers serving U.S. users, requires compliance with sanctions and lawful orders.

Does the DUSD ledger or minter currently have the technical ability to:

  • Freeze identified balances
  • Prevent transfers
  • Burn or seize tokens pursuant to a lawful order
  • Screen sanctioned addresses
  • Maintain an AML and sanctions-compliance program

If not, what prevents U.S. users from accessing DUSD until those controls and policies exist?

7. Where are the completed independent audits?

The materials allocate future funds to security and audits, but I have not found:

  • A completed independent smart-contract audit
  • Reproducible-build verification for every transferred canister
  • A reserve attestation by an independent accounting firm
  • An economic and oracle-manipulation risk assessment
  • A legal opinion covering U.S. availability

Plans to conduct audits later are not equivalent to completed due diligence before accepting public funds.

8. Who remains accountable after the SNS takes control?

Moving canisters to DAO governance does not automatically answer who is legally responsible for issuance, marketing, reserves, redemption, compliance, or losses.

Will responsibility remain with the DOXA Foundation, the developers, another issuer, participating service providers, or some combination of them?

“Decentralized” should not become a substitute for identifying the accountable legal party.

Requested protections for U.S. participants

Unless DOXA can provide a documented legal basis for U.S. participation, I believe the prudent course is to:

  1. Pause or restrict U.S. participation in the DOXA swap.
  2. Restrict U.S. access to DUSD minting, redemption, and staking until counsel confirms the applicable structure.
  3. Publish a legal and regulatory disclosure identifying the issuer, jurisdiction, licenses, redemption obligation, and U.S. legal analysis.
  4. Add a mandatory participant confirmation explaining that NNS approval is not regulatory approval, legal certification, an audit, or an endorsement.
  5. Publish completed security audits and reproducible-build evidence before representing the transferred system as production-ready.
  6. Explain what protections remain possible if the executed swap parameters can no longer be changed.

I would also appreciate clarification from DFINITY or knowledgeable NNS contributors on whether an NNS vote to create an SNS includes any legal-compliance review. Participants should not be left to infer that an executed governance proposal means a financial product has been approved for sale in their jurisdiction.

Conclusion

This is not an accusation that DOXA or DFINITY has violated U.S. law. It is a request for basic disclosures before Americans are invited to contribute assets to a stablecoin-related SNS.

The existing forum discussion addressed portions of DOXA’s economics, technology, team, and partnership claims. It did not answer these U.S. legal and participant-protection questions.

If DOXA has obtained qualified legal advice supporting U.S. participation, it should publish a meaningful summary now. If it has not, excluding U.S. participants until that work is completed is the safer and more responsible course—for Americans, the DOXA team, DFINITY, and the broader ICP ecosystem.

You’re a bit late to the party, mate.

Everybody already agreed.

The proposal vote is over; the decentralization swap is not. That makes these questions timely before U.S. participants contribute ICP.

An NNS vote is not a legal-compliance review and cannot waive laws applicable to people in the United States. If “everybody already agreed” on a compliant structure, please link to the answers covering the issuer, jurisdiction, U.S. legal analysis, reserves and redemption, yield, AML/sanctions controls, and lawful-order capability.

Otherwise, none of the questions raised here have actually been answered.

That sounds like a lotta work, mate.

No worries. You’re alright in my book.

My word is gold it is.

Update: NNS Motion Proposal 143662 Submitted — Urgent Action Requested

I have now submitted NNS Motion proposal 143662:

https://dashboard.internetcomputer.org/proposal/143662

Proposal 143605 may already be executed, but the DOXA decentralization swap has not yet begun. It is scheduled to open at 16:00 UTC on August 24, 2026, so these concerns are not moot and the window for protective action is extremely short.

The Motion asks for the following immediate response:

  • Determine publicly whether the executed swap can still be paused, delayed, cancelled, or amended to exclude U.S. participation.

  • If technically and lawfully possible, pause the swap or restrict U.S. participation until the project publishes a meaningful summary of qualified U.S. legal advice supporting that participation.

  • If neither action is possible, disclose that limitation immediately and display prominent warnings explaining that NNS approval is not regulatory approval, legal certification, a security audit, or an endorsement.

  • Publish the outstanding information concerning the issuer, U.S. legal basis, reserves and redemption, proposed yield, AML and sanctions controls, lawful-order capabilities, security audits, deployed canisters, and reproducible builds.

  • Clarify what legal-compliance, security, and participant-protection review—if any—occurred through the DFINITY grant or SNS-launch process.

This Motion does not declare that DOXA, DFINITY, or any NNS participant violated the law. It asks for precautionary action because the public record does not currently establish the legal basis for inviting U.S. persons to contribute ICP to this stablecoin-related SNS.

I respectfully ask:

  • NNS voters and known neurons to review proposal 143662 and vote directly and promptly.

  • DFINITY Foundation and the responsible NNS/SNS maintainers to respond before the swap opens, rather than waiting for the Motion’s voting period to conclude.

  • The DOXA team to answer the legal, reserve, redemption, yield, compliance, and security questions on the public record.

  • Anyone voting against the Motion to explain why allowing U.S. participation without these public disclosures provides adequate participant protection.

The DOXA project and its proposed stablecoin and SNS structure have been discussed and questioned publicly since 2024. This is not a last-minute objection merely because the concerns have now been consolidated into a formal Motion.

The swap is approaching. Please review and vote on proposal 143662 now.

Vote: Adopt.

Respect that we do.

I recommend NOT to attend on SNS sale. They have full control over everything (50+% Voting Power at start), including taking treasury ICP funds and run. There is no way anyone is going to Uganda to find this DOXA founder who most likely has different name, no money back. If you like to donate to most needy (DOXA founder), go ahead and throw money at Him.

Dear Henn,

I understand your concerns, but I believe there are a few important points that need clarification.

First, the SNS design does not simply give the team unrestricted control over 50% of everything. As you likely know from deploying or following SNS projects, governance power and token allocations are governed by the SNS configuration and neuron structure. In our case, the team neurons are locked for a full year, with long-term vesting in place. This was deliberately designed to align us with the long-term success of Doxa and to prevent immediate selling pressure.

Second, our primary objective has always been decentralization. We started building Doxa in 2023 and have continued for over three years. If our intention was simply to raise funds and disappear, we would not have spent years building through difficult periods, securing two DFINITY grants, and continuing to develop the project.

Third, the Doxa Foundation is a registered foundation and is subject to applicable legal and regulatory obligations. There is a real legal entity behind this project.

We are here for the long term, and our goal is simple: to decentralize Doxa and build something the ICP community can be proud of.

Ahhh - well if you promise it’s not shady, it can’t be!

fears alleviated… phew!

Status update: U.S. participation remains publicly unresolved

DOXA has responded to Motion proposal 143662 by referring to its governance-token designation, foundation registration, DFINITY grants, decentralization, and on-chain transparency.

Those statements do not answer the questions raised in this thread.

A DFINITY grant may demonstrate that a project received ecosystem-development support. It is not regulatory approval, a legal opinion, an independent security audit, or confirmation that a token offering may lawfully be made available in every jurisdiction. An NNS vote likewise should not be represented as legal or regulatory clearance.

Similarly, describing DOXA as a “governance token” does not by itself establish the legal treatment of the transaction through which it is offered. The SEC’s current crypto-asset interpretation expressly distinguishes between the classification of an asset and the circumstances in which that asset is offered as part of a transaction or investment contract.

On-chain visibility may show token movements and canister balances. It does not establish the issuer’s legal identity and jurisdiction, enforceable redemption obligations, reserve eligibility, completed audits, AML and sanctions controls, or the legal basis for offering participation to persons located in the United States.

Neither DOXA nor DFINITY has yet provided a documented answer addressing:

  • The specific legal entity responsible for the offering and for DoxaUSD issuance and redemption

  • The jurisdiction and regulatory status of that entity

  • The registration, exemption, exclusion, or other basis relied upon for U.S. participation

  • The legal treatment of the proposed DoxaUSD yield

  • Reserve eligibility and enforceable redemption rights

  • AML, sanctions, and lawful-order capabilities

  • Completed independent audits and reproducible-build evidence

  • What legal-compliance or participant-protection review, if any, occurred during the grant or SNS-launch process

Potential consequences of making the swap available in the United States

The executed swap configuration excludes participants from 23 countries but does not exclude the United States. Making an offering accessible to U.S. persons can create federal and state regulatory exposure depending on the facts, the applicable jurisdiction, and the legal treatment of the transaction.

If a competent regulator or court ultimately determines that applicable securities, antifraud, stablecoin, money-transmission, sanctions, or other laws were violated, legally available remedies may include:

  • Administrative stop orders or cease-and-desist orders

  • Temporary restraining orders and preliminary or permanent injunctions

  • Subpoenas, accountings, expedited discovery, and evidence-preservation orders

  • Appointment of a receiver or conservator

  • Preservation or freezing of assets

  • Rescission and restitution for eligible purchasers

  • Disgorgement of proceeds and interest

  • Civil monetary penalties

  • Referral for criminal investigation where the evidence warrants it

  • Private rescission or damages claims by qualifying purchasers

For example, Maryland Corporations and Associations Code §11-702 authorizes the Maryland Securities Commissioner, when the statutory requirements are satisfied, to seek an injunction, receivership, asset freeze, rescission, restitution, disgorgement, penalties, and other appropriate relief.

Those are potential remedies available to regulators, courts, or legally eligible purchasers. I am not claiming that a violation has already been adjudicated, that every remedy applies, or that an individual forum participant can unilaterally freeze the treasury.

The existence of these potential consequences is precisely why documented legal analysis should have preceded—not followed—the decision to make the swap accessible to U.S. participants.

Until a meaningful summary of qualified U.S. legal analysis and appropriate risk disclosures are published, my recommendation is that persons located in the United States refrain from participating in the DOXA decentralization swap.

That is a precautionary participant-protection recommendation—not a declaration that DOXA, DFINITY, or any other party has violated the law.

I again invite DOXA and DFINITY to provide factual, documented answers on the public record. Repeating assurances about grants, decentralization, project longevity, or on-chain visibility does not resolve these questions.

What questions where asked, im pretty sure this Doxa scam is not run by me. Phasma, do you see something i dont or you again trolling?

Technical follow-up after adoption of NNS Motion 143662: Is an executable emergency patch possible?

NNS Motion proposal 143662 was adopted and received more Yes voting power than the original DOXA SNS-creation proposal 143605.

That result deserves a direct technical response. However, because proposal 143662 was a Motion, it expressed an NNS position but did not itself alter code or execute an intervention.

I want to narrow this follow-up to an implementation question. I am not asking engineers to adjudicate whether U.S. law has been violated. I am asking what authorized, auditable technical mechanisms remain available while U.S. eligibility is publicly unresolved.

The relevant live canisters are:

  • SNS Root: bu3tj-cqaaa-aaaaq-aafdq-cai
  • SNS Governance: azvxh-nyaaa-aaaaq-aafea-cai
  • SNS Swap: axx2p-wiaaa-aaaaq-aaffa-cai

What the current source appears to show

First, the current Swap implementation does not appear to provide an ordinary early-abort mechanism. Its can_abort logic permits an abort only when the swap has ended—because the deadline or maximum target was reached—and participation remains insufficient:

https://github.com/dfinity/ic/blob/master/rs/sns/swap/src/swap.rs#L2714-L2727

Second, simply stopping the Swap canister would not be a proper remedy. Refund processing requires the lifecycle to be ABORTED or COMMITTED. Stopping the canister would apparently freeze the current state without transitioning the swap, refunding contributors, or restoring fallback controllers:

https://github.com/dfinity/ic/blob/master/rs/sns/swap/src/swap.rs#L1787-L1816

Third, the country restrictions appear to be enforced primarily by the NNS dapp interface. The current frontend code expressly enables participation when its country lookup returns an error:

https://github.com/dfinity/nns-dapp/blob/main/frontend/src/lib/utils/projects.utils.ts#L352-L369

The on-chain Swap contribution path appears to validate lifecycle, contribution limits, and any configured confirmation text, but I do not see a jurisdiction check:

https://github.com/dfinity/ic/blob/master/rs/sns/swap/src/swap.rs#L1066-L1147

Therefore, merely adding the United States to restricted_countries or changing the NNS dapp would provide a useful official-interface protection, but it would not appear to create a reliable on-chain exclusion and could potentially be bypassed by direct canister interaction.

An executable upgrade may nevertheless be possible

The NNS proposal documentation identifies:

  • AddSnsWasm, which publishes a new SNS framework Wasm
  • InsertSnsWasmUpgradePathEntries, which can create an upgrade path for all SNSes or a specific SNS

https://docs.internetcomputer.org/references/nns-proposal-types/

The SNS framework documentation also states that existing SNS instances can upgrade through NNS-approved upgrade paths:

https://docs.internetcomputer.org/concepts/sns-framework/

This suggests that a code-bearing response may be technically possible in principle, but it would require engineering and governance—not another general Motion.

Questions for DFINITY and SNS framework maintainers

Please provide a direct answer to the following:

  1. Can the live DOXA Swap safely be paused, amended, or transitioned to an early-aborted state through any presently authorized proposal or canister method?

  2. If no existing method permits that action, can a reviewed Swap Wasm add an emergency mechanism that:

    • Stops accepting new contributions
    • Preserves the existing state
    • Safely refunds current contributors
    • Restores the intended fallback controllers
    • Permits a corrected SNS launch proposal afterward?
  3. Can AddSnsWasm and an SNS-specific InsertSnsWasmUpgradePathEntries proposal deliver that patch to DOXA while its governance canister remains in PreInitializationSwap mode?

  4. Would another proposal or authorized call then be required to invoke the new behavior? If so, what exact proposal type, controller path, and payload would be required?

  5. If this is feasible, will the responsible maintainers identify:

    • An implementation owner
    • The source-code pull request
    • Reproducible-build instructions and Wasm hash
    • State-migration and refund tests
    • The exact executable proposal sequence
    • A timeline before the scheduled September 14, 2026 swap deadline?
  6. Pending that work, can the NNS dapp immediately display a prominent warning and temporarily disable ordinary participation through the official DOXA page for users identified as being in the United States?

A suitable warning would be:

U.S. eligibility has not been publicly established. Persons located in the United States should not participate unless the responsible issuer publishes qualified U.S. legal analysis and appropriate eligibility controls. NNS approval is not regulatory approval, legal certification, a security audit, or an endorsement.

The interface should also disclose that any frontend restriction may not prevent direct canister interaction.

If none of these measures is technically possible, please say so explicitly and identify the exact protocol or controller limitation. The community needs a concrete technical answer—not another general assurance.

I do not recommend spending another 50 ICP on a proposal until maintainers provide reviewed code, a reproducible Wasm, an exact executable payload, and a safe plan for current contributors.

Until the U.S. basis and appropriate controls are documented, my precautionary recommendation remains that persons located in the United States refrain from participating.

Request for public engineering-ticket tracking

A brief GitHub-tracking update: public issue creation is unavailable in the dfinity/ic repository, while the dfinity/nns-dapp issue tracker expressly restricts creation of new issues.

I have therefore asked DFINITY Support to create and cross-link two internal engineering tickets:

  1. SNS Swap lifecycle: Determine whether an authorized, state-safe mechanism exists—or should be added—to pause or terminate an active swap, prevent new contributions, refund existing contributors exactly once, and restore fallback controllers.
  2. NNS dapp participation controls: Review the current fail-open country-lookup behavior and consider an explicit error state, configurable warnings, and an authorized official-interface participation disable mechanism, with disclosure that frontend restrictions remain bypassable.

This is a request for technical analysis and public tracking, not a request for GitHub maintainers to decide any legal question.

Could a DFINITY or SNS-framework maintainer please provide the resulting ticket numbers, responsible teams, and public links if available? These should be cross-referenced with adopted NNS Motion proposal 143662:

https://dashboard.internetcomputer.org/proposal/143662

Yeah… and? You could apply that ‘if’ to many launches. Participants participate at their own risk, and I agree that this is not a smart investment. Doesn’t mean the NNS or DFINITY needs to do anything though, particularly not pre-emptively. Also, what you’re demanding effectively means demanding the centralisation of what is supposed to be a DAO by demand a specific ‘legal representative’.

Put your LLM on chill mode please

“At your own risk” does not answer the questions raised, nor does it eliminate obligations that may apply to an offeror or issuer. I expressly described the listed remedies as conditional and did not claim that any violation has been adjudicated.

Nor am I demanding that a DAO appoint a centralized controller. DOXA has publicly stated that a registered foundation exists. The factual questions are which existing entity is responsible for offering DOXA, which entity will issue and redeem DoxaUSD, and which entity controls or owns the reserves. Decentralized governance does not make those responsibilities or disclosures disappear.

The NNS has now adopted Motion 143662. Whether DFINITY or the NNS has an obligation or technically authorized mechanism to intervene is precisely one of the questions placed before the maintainers; it is not resolved by saying participants assume risk.

More importantly, my latest follow-up asks narrow technical questions: whether the active swap can safely be paused, amended, upgraded, or transitioned to an early-aborted state; how contributors could be refunded; whether fallback controllers could be restored; and whether the official NNS interface can display a warning or disable ordinary participation while the issue is reviewed.

Your response does not address any of those implementation questions. If you know the relevant controller path, proposal type, upgrade restriction, or source-code limitation, please provide it. Otherwise, those questions remain open for DFINITY and the SNS-framework maintainers.

And as for the LLM jab: my agents do my bidding. Don’t yours? The source code, canister IDs, proposal result, and unanswered questions remain the same regardless of which tools helped analyze them.

… The DAO, and whoever collectively has the controlling stake at any point in time, which can change at any point in time. All of your other questions are moot points

Now ask you LLM to stop waffling and go and build something or summat

Oops, wrong tag :joy:
Definitely not Phasma—my tagging skills just decided to troll me.

Okay, now I’ve got the right tag :joy:
I didn’t think @kizzafredrichkibalam would answer the question here anyway.

I’m sure they mean well.

Nobody would do that for no reason, mate.

I think everybody agrees.