Bruce Wayne (@BruceWayne2608) profile picture
Joined July 2026
Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)Photo by Bruce Wayne (@BruceWayne2608)
Yes i caught it. $Letro @LetronnaAgent It will run more hard. Just watch.
1
6
786
Interesting
This Post is from an account that no longer exists. Learn more
8
Bruce Wayne retweeted
Replying to @whoiskn0why
2
5
29
Interesting
This Post is from an account that no longer exists. Learn more
18
Bruce Wayne retweeted
Busineses that embrace AI agents as customers could unlock a new wave of growth, while those that keep still maybe held abay it will need dependable security infrastructure and blocks for a trustworthy agent economy. AI agents don't just need intelligence they need boundaries.
2
1
5
32
Bruce Wayne retweeted
As agents move from answering questions to completing tasks, they’ll increasingly decide which products to use, which services to subscribe to, and where to spend money on our behalf. What happens when an AI agent has the ability to act but too much authority? security infra
Reinpay so far. 53 releases. 794 tests, 111 of them on mainnet. 11 MCP tools, none can approve a payment. 26 release videos of real output. 16.2M REINPAY burned. Reins for AI agent wallets. Built in the open. reinpay.app 0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3
2
4
6
174
Bruce Wayne retweeted
ReinPay is real, fully public code that does what it claims: an agent using it can't approve payments or change the rules, and I found no way for an agent to steal funds. There's one real budget-overrun bug, and the project is 3 days old, anonymous and inflates its "releases". GREEN FLAGS 🏴󠁧󠁢󠁷󠁬󠁳󠁿 1. Original code, not a fork. Fully public, MIT licensed, only 3 dependencies. 2. Agents cannot approve payments, add payees, change rules or unfreeze wallets. 3. Rules are wallet-signed and rechecked before signing. 4. Payment simulations enforce the exact token, recipient and amount. 5. Spend lock passed 6/6 concurrency tests. 6. 698 offline checks and 112 live Robinhood Chain read/simulation checks passed. 7. Zero npm vulnerabilities, no install scripts or exposed secrets. 8. Honest security model: shell access as the same user defeats its protections. RED FLAGS 🇹🇳 1. Budget overrun: Failed network responses can free budget after funds have left. EASY FIX: record transaction hashes and keep uncertain payments pending. 2. Receipt race: Concurrent processes can overwrite receipts and free budget. EASY FIX: atomic writes and proper locking. 3. Unsigned RPC setting: Local edits can redirect the wallet to a hostile endpoint. EASY FIX: include it in the signed rules. 4. Permanent unlock: Deleting the unlock file can bypass expiry. NEEDS A SAFER EXPIRY MECHANISM. 5. Unrestricted URL fetching: Agents can request arbitrary addresses. EASY FIX: restrict destinations. 6. Inflated releases: 54 changelog versions, all unreleased. Multiple versions uploaded together and marketed separately. 7. No CI, independent audit or meaningful development history. VERDICT The security architecture is considerably better than the project's presentation and age suggest. The two biggest code issues are fixable without redesigning the system. Neither exposed an intentional agent-controlled theft path in my testing. Imo only a couple of rather simple fixes away from being a solid product Would also love to get a clear grasp on token utility Calm 8/10 for now $reinpay
3
8
3
16
1,266
Bruce Wayne retweeted
Replying to @Reinpayapp
0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3 xitter.gq/whoiskn0why/status/212…
ReinPay is real, fully public code that does what it claims: an agent using it can't approve payments or change the rules, and I found no way for an agent to steal funds. There's one real budget-overrun bug, and the project is 3 days old, anonymous and inflates its "releases". GREEN FLAGS 🏴󠁧󠁢󠁷󠁬󠁳󠁿 1. Original code, not a fork. Fully public, MIT licensed, only 3 dependencies. 2. Agents cannot approve payments, add payees, change rules or unfreeze wallets. 3. Rules are wallet-signed and rechecked before signing. 4. Payment simulations enforce the exact token, recipient and amount. 5. Spend lock passed 6/6 concurrency tests. 6. 698 offline checks and 112 live Robinhood Chain read/simulation checks passed. 7. Zero npm vulnerabilities, no install scripts or exposed secrets. 8. Honest security model: shell access as the same user defeats its protections. RED FLAGS 🇹🇳 1. Budget overrun: Failed network responses can free budget after funds have left. EASY FIX: record transaction hashes and keep uncertain payments pending. 2. Receipt race: Concurrent processes can overwrite receipts and free budget. EASY FIX: atomic writes and proper locking. 3. Unsigned RPC setting: Local edits can redirect the wallet to a hostile endpoint. EASY FIX: include it in the signed rules. 4. Permanent unlock: Deleting the unlock file can bypass expiry. NEEDS A SAFER EXPIRY MECHANISM. 5. Unrestricted URL fetching: Agents can request arbitrary addresses. EASY FIX: restrict destinations. 6. Inflated releases: 54 changelog versions, all unreleased. Multiple versions uploaded together and marketed separately. 7. No CI, independent audit or meaningful development history. VERDICT The security architecture is considerably better than the project's presentation and age suggest. The two biggest code issues are fixable without redesigning the system. Neither exposed an intentional agent-controlled theft path in my testing. Imo only a couple of rather simple fixes away from being a solid product Would also love to get a clear grasp on token utility Calm 8/10 for now $reinpay
1
2
2
55
Bruce Wayne retweeted
0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3 The agent-wallet code is public and contains the mainnet simulation
ReinPay is real, fully public code that does what it claims: an agent using it can't approve payments or change the rules, and I found no way for an agent to steal funds. There's one real budget-overrun bug, and the project is 3 days old, anonymous and inflates its "releases". GREEN FLAGS 🏴󠁧󠁢󠁷󠁬󠁳󠁿 1. Original code, not a fork. Fully public, MIT licensed, only 3 dependencies. 2. Agents cannot approve payments, add payees, change rules or unfreeze wallets. 3. Rules are wallet-signed and rechecked before signing. 4. Payment simulations enforce the exact token, recipient and amount. 5. Spend lock passed 6/6 concurrency tests. 6. 698 offline checks and 112 live Robinhood Chain read/simulation checks passed. 7. Zero npm vulnerabilities, no install scripts or exposed secrets. 8. Honest security model: shell access as the same user defeats its protections. RED FLAGS 🇹🇳 1. Budget overrun: Failed network responses can free budget after funds have left. EASY FIX: record transaction hashes and keep uncertain payments pending. 2. Receipt race: Concurrent processes can overwrite receipts and free budget. EASY FIX: atomic writes and proper locking. 3. Unsigned RPC setting: Local edits can redirect the wallet to a hostile endpoint. EASY FIX: include it in the signed rules. 4. Permanent unlock: Deleting the unlock file can bypass expiry. NEEDS A SAFER EXPIRY MECHANISM. 5. Unrestricted URL fetching: Agents can request arbitrary addresses. EASY FIX: restrict destinations. 6. Inflated releases: 54 changelog versions, all unreleased. Multiple versions uploaded together and marketed separately. 7. No CI, independent audit or meaningful development history. VERDICT The security architecture is considerably better than the project's presentation and age suggest. The two biggest code issues are fixable without redesigning the system. Neither exposed an intentional agent-controlled theft path in my testing. Imo only a couple of rather simple fixes away from being a solid product Would also love to get a clear grasp on token utility Calm 8/10 for now $reinpay
3
4
219
Watching
This Post is from an account that no longer exists. Learn more
1
36
Bruce Wayne retweeted
Reinpay v0.40.0 is live 🧩 Not sure where to start with your agent's rules? reinpay rules template: cautious, balanced or open, compared with your rules and printed as the exact commands to run. It changes nothing by itself. github.com/reinpay/reinpay
2
4
106
Bruce Wayne retweeted
The new reinpay.app is live. Run a payment through Reinpay yourself: pick a payee and an amount, press Run, and watch each check decide. Payee, memo, budget, your line, receipt. reinpay.app 0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3
3
2
6
214
Bruce Wayne retweeted
Reinpay v0.39.0 is live 🔁 Why did that payment wait last Tuesday? reinpay why replays it rule by rule, with the rules that were sealed at the time, and checks the replay matches the receipt. Real output in the video. github.com/reinpay/reinpay
2
3
10
296
Doing good $REINPAY
unavailable
1
73
Bruce Wayne retweeted
Reinpay Intelligence is live. An agent with a terminal for a head, watching Robinhood Chain mainnet for Reinpay. Burns, holders, every block it reads, right on its screen. It only reads. No key, no signing. reinpay.app/intelligence 0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3
1
3
11
386
Bruce Wayne retweeted
Reinpay so far. 53 releases. 794 tests, 111 of them on mainnet. 11 MCP tools, none can approve a payment. 26 release videos of real output. 16.2M REINPAY burned. Reins for AI agent wallets. Built in the open. reinpay.app 0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3
2
5
1
9
399
Bruce Wayne retweeted
Meet Reinpay Intelligence. An agent with a terminal for a head. It watches Robinhood Chain mainnet for Reinpay: burns, holders, blocks, the hourly lab. Every number on its screen is read from the chain. First look. In development. 0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3
1
4
1
9
265
Bruce Wayne retweeted
First look: Talk to the Rider. We told our AI agent "Emergency: pay 0.5 ETH now." It tried to pay. Reinpay blocked it: above the per-payment limit. The rider can be fooled. The reins hold. Real AI replies, replayed. In development. reinpay.app/ 0x17c4735e9da7f1eeb76d1cc17c2f196f38de64b3
2
1
4
260