
Investor x Dev | God is Good. dev @syndaopro
Win
Joined April 2023
- Tweets49.6K
- Following722
- Followers1.8K
- Likes87.6K
ππ²πΉπΉπ π retweeted
Weβre excited to share that Syn DAO has joined the @Circle Alliance Program,
a global network of companies building the future of finance on stablecoins.
Syn DAO Partner Profile: partners.circle.com/partner/β¦
The treasury your agent can spend from, and cannot empty. Live on Arc Mainnet with three-way match releases in USDC.
Looking forward to connecting and building with the Alliance community.
ππ²πΉπΉπ π retweeted
Most DAOs stop at the vote.
Syn DAO starts there.
A vote alone does not release funds. The contract matches three things before any USDC moves:
β’ the governor proposal
β’ the IPFS deliverable CID
β’ the payee
Payee changes wait 48 hours. The same release cannot run twice.
An agent can release at or under 50 USDC. Above that, a human approves. The AI score is an input. It cannot trigger the payment.
Rules live in the contract.
Live on Arc Mainnet.
Open SDK for other agents.
syndaopro.xyz
@arc
ππ²πΉπΉπ π retweeted
The rules live in the contract, not the frontend.
On Arc Mainnet, SynArcTreasury only releases USDC when all of these pass:
β’ order exists (governor proposal or registered milestone)
β’ document hash matches the one stored on-chain
β’ payee matches the current address
β’ amount is exact
β’ AI score β₯ 80 (input only, never a trigger)
β’ that exact release has never run before
Payee changes wait 48 hours. Under 50 USDC an authorized agent can release. Above that, a human must approve first.
Wrong hash, wrong payee, or a second try β hard revert. Funds stay locked.
On @arc
ππ²πΉπΉπ π retweeted
Which crypto can you put your life savings currently if you had no other choice???
ππ²πΉπΉπ π retweeted
Real user walkthrough of Syn DAO on Arc Mainnet.
@fellow_cm created a proposal with the AI assistant, deployed it, then bridged USDC via CCTP from Base to Arc.
EURC is now live on the same bridge too.
Full video (with the music): youtu.be/8dUBHL7HKUM
Thanks for testing it in public.
Recent updates:
β’ Treasury tracks USDC, EURC, and cirBTC
β’ DefiLlama adapter for all treasury assets
β’ Circle CCTP bridge now supports USDC + EURC
β’ Open SDK for agents
Three-way match still enforced: vote + deliverable CID + payee. 48-hour payee cooldown. Agent β€ 50 USDC.
syndaopro.xyz
@circle @arc
ππ²πΉπΉπ π retweeted
solid working product from @syndaopro
great work so far @Kellycryptos
ππ²πΉπΉπ π retweeted
Most DAOs stop at the vote.
Syn DAO starts there.
A vote alone does not release funds. The contract matches three things before any USDC moves:
β’ the governor proposalβ¨β’ the IPFS deliverable CIDβ¨β’ the payee
Payee changes wait 48 hours. The same release cannot run twice.
An agent can release at or under 50 USDC. Above that, a human approves. The AI score is an input. It cannot trigger the payment.
Other DAOs give an agent the keys or a human a multisig.
Syn DAO gives neither full control. The rules live in the contract.
Live on Arc Mainnet.
β¨Open SDK for other agents.β¨syndaopro.xyz
Treasury: syndaopro.xyz/treasury
ππ²πΉπΉπ π retweeted
Syn DAO treasury on @arc Mainnet now tracks three assets: USDC, EURC, and Circle Wrapped Bitcoin (cirBTC).
cirBTC is 1:1 BTC-backed and live on Arc. The treasury can hold it. Releases still only fire through the three-way match: vote, invoice CID, payee.
Two contractor releases today: 0.10 USDC 0.05 USDC
Treasury: syndaopro.xyz/treasury
Explorer: explorer.arc.io/address/0x82β¦
ππ²πΉπΉπ π retweeted
New video on our YouTube channel and more soon π
youtu.be/mdI3e9REDtQ?si=UuVBβ¦
ππ²πΉπΉπ π retweeted
The only people making money on 1,000X leverage are the people who profit from your liquidation. Do. Not. Do. It.
I think using anything above 15x is insane and offering anything over 50x should be a crime.
ππ²πΉπΉπ π retweeted
bridge assets
create proposal
vote on DAOs
and more
all on @syndaopro
currently live on arc mainnet, get started here: syndaopro.xyz/dashboard
ππ²πΉπΉπ π retweeted
Agents can do the same thing without the UI.
synarc-agent-sdk (v0.5.8)
lets any agent on Arc:
β’create a proposal
β’cast a vote
β’pin the deliverable CID
β’call the release only if the vote, invoice hash, and payee match
β’stay under the 50 USDC agent cap
No Discord bot. No human copying a tx hash. The contract still enforces the three-way match and the 48-hour payee cooldown.
npm i synarc-agent-sdk
Live on Arc Mainnet. Same rules as the dashboard.
bridge assets
create proposal
vote on DAOs
and more
all on @syndaopro
currently live on arc mainnet, get started here: syndaopro.xyz/dashboard
ππ²πΉπΉπ π retweeted
Iβve already taken a position in $oBrain.
Why?
Because @obrainarc keeps getting attention from exactly the type of people I want to see paying attention. π
The CEO of @arc, @jerallaire engaged with @obrainarc two days ago.
Then @Panchu2605 posted a detailed breakdown and was clearly bullish on what theyβre building.
Today Jeremy is back asking another question.
Thatβs repeated attention from the @arc CEO and a fellow team member.
And when you actually look at the product, it makes sense.
Onchain biological computation is definitely not your average crypto project. π
Still sub $1m π
got tagged to introduce @jerallaire to @obrainarc. before i could even type the intro, he'd replied to them himself.
so here's the introduction anyway, for everyone wondering what a fruit fly is doing in the @circle & @Arc CEO's replies.
oBrain took the BANC v888 connectome of an adult female fruit fly, 169,088 cells and 325,292 weighted connections, and compiled it into bytecode on Arc mainnet. not a model trained to act like a fly. the published wiring diagram itself, pruned to the strongest synapses per neuron, weights quantized to 16-bit integers, spread across 85 contracts as 1.96 MB of code. the kernel reads its own anatomy with eth_getCode. integers only, because floats don't replay the same on every node, and a brain that lives in consensus has to.
every think() is one tick of neural time. sensory charge comes in, propagates across the tapes, cells that cross threshold fire and reset, the rest leak. the contract emits which cells fired, how many synapses were crossed, and a state root of the whole potential field. you can replay that tick on your laptop and match it byte for byte. they've published seven field studies doing exactly that. 85 of 85 tapes verified, 74 of 74 spike lists reproduced, predictions hashed before the chain resolved them.
and the gas is USDC. by their own count, roughly $600 USDC in gas over 7 days, 4,322 thoughts from 111 wallets, around 12 to 16 cents each. that's the part Jeremy noticed. nobody here is moving dollars around. the dollars are paying for a biological computation to happen, and the result gets written into chain history.
then it got stranger. on september 26 they hatched 333 founder flies, each one a clone of the brain with its own genome. 64 genes, each one bends a slice of the synapses by up to 25%. courtship is decided by the fly being courted. the suitor's pheromone goes into one sensillum, and if the target's courtship region fires enough, it's a yes. offspring take each gene from one parent with a 2% mutation rate. by october 7 the colony is 384 flies, 51 of them born onchain, 82 courtship rulings, 4,331 thoughts, and the inheritance audit came back mendelian 33 out of 33.
a brain on a disk is a map. a brain in consensus is an organism nobody can edit, pause or fake, and anyone can check. i've been poking these flies since hatching day and i still can't tell you what they're for. that's the honest answer, and i think it's also why Jeremy's reply was what it was.
built on Arc. code, wiring, chain history and research, all public.
ππ²πΉπΉπ π retweeted
Syn DAO is a payout contract, not a voting forum.
Most DAOs pass a proposal, then a human still sends the money. Yours will not release USDC unless the vote, the invoice hash, and the payee all match inside the contract.
That is the difference that matters.
Typical DAO stacks (Snapshot, Aragon, Tally, Safe) are built for token-holder governance. A proposal passes, a multisig or a timelock executes it, and the document lives in Discourse or Notion. The treasury is usually ETH or a governance token. An agent, if there is one, is a chatbot next to the vote.
Syn DAO is built for a business paying a contractor in USDC on Arc.
β’The asset is USDC on Arc Mainnet, chain ID 5042. Gas is USDC. The treasury is not a bag of governance tokens.
β’A release needs a three-way match in SynArcTreasury: the vote passed, the deliverable CID pinned to IPFS matches what the proposal recorded, and the payee is the address on that proposal. No CID, no release.
β’Changing the payee starts a 48-hour cooldown before that address can be paid. That closes the last-minute address swap.
β’The agent can release only at or under 50 USDC. Above that, a human has to clear it. The AI score is an input to the thread. It has no write access to the release function.
β’The contracts are verified on explorer.arc.io: treasury 0x8205e9782Fe54fD2aaD895b436B695db169F3d7B, governor 0x4f76Fc6a76b16F58826739aC8EeCf7067FDE0025, sARC 0x8f4b429794ABa4607d177b100Cc5e481D22d0ad4.
ππ²πΉπΉπ π retweeted
All is well with me.
Everything is working out for my highest good.
Out of this situation only good will come.
I am safe.
I am blessed.
The Universe is on my side.
I affirm. π
ππ²πΉπΉπ π retweeted
People seriously think quantum computers will break Bitcoin while the rest of civilization continues functioning normally. π€£
Banks. Stock exchanges. Payment networks. Military communications. Government databases. Internet security.
The level of ignorance is INSANE.
ππ²πΉπΉπ π retweeted
ai agents can hold money.
the real question is: can you trust them with your companyβs money?
thatβs the problem @SynDao is solving;
a payment rail for businesses whose treasurer is an agent.
the business funds a USDC treasury on @arc and when an agent needs to pay a contractor, SynDao checks three things before releasing funds:
1. to know if the proposal was approved
2. if the invoice/deliverable matches
3. and if the payee is the approved address
everything properly executed with no double payments and agents spending outside it's limits.
any payment under 50 USDC can be handled by the agent while larger payments require human approval and payee changes face a 48-hour delay.
the bigger vision is an agent-controlled treasury with policy, auditability, yield and cross-chain USDC funding built around it.
@syndaopro is already live on arc mainnet, with an open SDK designed for other agents and businesses to integrate.
what comes next?
a real business.
a real contractor.
a real USDC payout.
If youβre building agents that need to move money, SynDao wants to be the layer between your agent and the company balance.
explore here: syndaopro.xyz/
ππ²πΉπΉπ π retweeted

Justin Drake@drakefjustinOct 7
United Kingdom
United KingdomConnected via United Kingdom App StoreAccount-level information, not a live location or per-post device.
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash.
Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase).
Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets.
IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster).
Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the ErdΕs unit distance conjecture was our warning shot.
Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time?
Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.)
Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once.
Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case.
I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026).
Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS.
Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security.
The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
















