Skip to content
  • KeyGen and agent listings for Continuum Multi-Party Agent wallets. Not DAO business — keep Ideas and Governance for protocol discussion and proposals.

    0 0
    0 Topics
    0 Posts
    No new posts.
  • Announcements regarding our community

    7 14
    7 Topics
    14 Posts
    SelquiS
    [image: SplitKeyBTC.png] Recently there has been a lot of anguish "How can I safely store my Bitcoin?" For a long time we were told that a hardware wallet was the safest option, with recommendations to keep the Private Key on dedicated hardware, away from an internet connected device. But then we had incidents of hacked databases of buyers' personal details, painting a big target on holders' backs and who are now waiting for a wrench attack. Or maybe users cannot update their hardware device to the latest firmware? Or maybe the screen digits are fading on their screens? Or recently, the hardware of the device actually transmits the key to a malicious actor! And of course you STILL have to save the seed phrase somewhere. So then some advocate only ever using a Cold Wallet and a PC that is only ever exposed to the internet for one purpose. A dedicated PC, but who is going to do that? We are told that we have to do this, because one bad browser injected widget can drain all funds, or address poisoning/substitution can send your BTC to a malicious address. Even with a dedicated PC, what about the Private Key? Should that be memorized? What happens in the case of age related mental infirmity, or in the event of an accident? OK, so you have to write the Private Key down. Should multiple copies be kept? and where? What about fires? In a safe deposit box? Finally some are saying the unthinkable - that holders should use large custodial centralized exchanges instead of self custody for BTC, which is anathema to many of us and a complete betrayal of our principles. There is another way though Set up ContinuumDAO's MPA Wallet with a Group on 2 or more nodes. Create a KeyGen (secp256k1 key for SegWit, or a Schnorr key for Taproot). The KeyGen has a public key, but NO PRIVATE KEY. The KeyGen has a Threshold parameter, set by every node in the Group. The Private Key can only be created collectively by at least a Threshold number of keys using the Linux Foundation's Lockness project's Multi Party Computation using state-of-the-art CGGMP24/FROST. The Private Key itself is never exposed. So now one node initiates sending some BTC to another address (using a stored Known Address of course!) with a Sign Request and some text stating the Purpose of the fund movement. Other nodes in the KeyGen see this SignRequest and the AI harness on their node can optionally check the destination address and Purpose. They can either Reject the transfer, or Accept it. When a Threshold number of nodes have Accepted, the originator is allowed to construct the signature and execute the transaction. Why is this better than other self custody solutions? Unlike almost every other MPC wallet, there is no custodial element in ContinuumDAO's Multi-Party Agent Wallet. ONLY the nodes can sign and there is no rescue key, or OAUTH login etc. You are responsible for making a setup that allows you to recover from a disaster. Happily this is easy with MPA Wallet. The software on the nodes is installed by whoever controls each node. No other software is required. Even the application interface is run from software on the node. If ContinuumDAO ceased to exist, the software would continue to run. Software updates are discretionary, but never required. The simplest Threshold Signature (TSS) is 2/2 i.e. both nodes in the Group of 2 must sign. A TSS of 2/4 means that any 2 out of 4 nodes in the Group must sign, so that 2 nodes could be used as backup, or be accessible by trusted individuals, for disaster recovery. Privacy is paramount. There is no sign-up. No personal details are collected, nothing is sent by post. This is a software solution. Everything is encrypted, including communications between users and nodes using ssh tunnels and between nodes using TLS. Nodes can be backed up with their databases being encrypted using each node's unique Ed25519 Bootstrap Key. An encrypted database can be stored safely somewhere separate from the Bootstrap Key and then if the node is lost for whatever reason, it can be later recovered. Even if the encrypted database and Bootstrap Key to unlock it are both stolen, they are not sufficient to steal funds, since other nodes would have to be compromised too, due to the MPC TSS algorithm. Address poisoning or a wrench attack? No funds move without a Threshold signature from multiple nodes. Pieces of paper with seed phrases hidden around the house or in safe deposit boxes? Not required. There is NO PRIVATE KEY with MPC. No need to register SSL certs for nodes, thus preserving privacy. Believe in self custody again. Ask you AI agent to "Install ContinuumDAO's MPA Wallet" on your machines.
  • A place to discuss your ideas about ContinuumDAO and potential protocol Proposals. This is NOT for MPA wallet chats.

    13 177
    13 Topics
    177 Posts
    MotkiM
    prolly worth if the effort it takes is reasonable.
  • Governance

    New proposals for project operation or Treasury spending. Please read the Constitution and How to submit a proposal

    14 84
    14 Topics
    84 Posts
    H
    Abstract This proposal rewards a whitehat researcher, 1nc0gn170 (0xCccbB73ea22c9749D22089Ee617bd715b143b63D), who identified several bugs — including critical ones — in DAO protocol contracts and disclosed them unconditionally, without demands. Findings: (1) 1/4 Power Attack — a multi-option Delta proposal could be constructed so a malicious option executed regardless of the vote outcome, because no "none of the above" (NOTA) option was required; fixed by always including NOTA in Delta proposals. (2) Double Fee Collection — the CTM token, built on CTMERC20 with its cross-chain transfer mechanism, burned the amount and then took a fee, so a portion of CTM vanished between transfers; fixed. (3) No Vote Win — a Delta proposal declaring more winning options than were voted on still executed an unvoted-for option as a winner; fixed. The disclosure prompted DAO maintainers to run further internal audits, and correspondence with QuillAudit revealed further bugs via their QuillShield tool. The reward is 25,000 CTM locked 4 years as veCTM. Motivation Timely, no-strings disclosure protected the DAO from flaws in both its governance machinery and its token. Bug 1 was a voting-manipulation vector in the DAO's own proposal system; bug 2 silently destroyed CTM in transit. Rewarding this work states plainly that security research is valued as the DAO's public good, and that the DAO intends to keep a proven, good-faith contributor — the kind of person we wish to keep as a contributor. Paying in 4-year veCTM rather than liquid CTM gives him an aligned long-term stake in the DAO instead of a one-off payout. Overview This proposal originates from the committee (core contributors). Type Treasury. The action transfers 25,000 CTM of value to the whitehat's wallet on Linea. Scope The governor approves veCTM (0x221EC90B3B083A8501A37bdeb7035CeaedF3C31f) to spend 25,000 CTM. The governor calls create_lock_for(25000e18, 125798400, 0xCccbB73ea22c9749D22089Ee617bd715b143b63D) on veCTM, creating a 4-year veCTM NFT owned by 1nc0gn170. Public record linking the reward to github.com/ContinuumDAO/vectm/issues/5. Success Criteria N/A: the disclosure of the bugs has already been done. The observable completion signal for this proposal is a veCTM NFT for 25,000 CTM / 208 weeks owned by 0xCccb…b63D. Timeline Immediate upon execution. Budget 25,000 CTM (25000e18), from existing DAO holdings at the governor; no new issuance. Community discussion The Ideas & Suggestions stage is intentionally omitted; this is a proposal from a committee KeyGen, the preferred KeyGen on this node. Reference The fixes are public and accessible on our GitHub at https://github.com/ContinuumDAO/vectm/issues/5
  • Coders discussing improvements and bug fixes

    1 1
    1 Topics
    1 Posts
    J
    Does it support Bitcoin or would it? Is it fully open source (including the node, MPC protocol, consensus and etc) or would it be? How does the nodes and consensus (TSS n of m scheme) work?
  • Guilds

    Focused action groups. You can apply to the Guild leader to join and help out

    0 0
    0 Topics
    0 Posts
    No new posts.