Syv 🪐 (@0xSyv) profile picture

What if?

Jupiter
Joined November 2023
Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)Photo by Syv 🪐 (@0xSyv)
Syv 🪐 retweeted
THE BLOCK: Ethereum Foundation researcher Justin Drake is urging the crypto industry to begin planning for "bunker mode," recommending a controlled migration of assets to fresh addresses that have never signed a transaction, keeping their public keys hidden behind a hash. Drake said it is now reasonable to prepare for the possibility that AI could enable fast recovery of private keys from ECDSA public keys, potentially within "months not years." "Don't rush," Drake said, warning that a disorderly migration could cause more harm than good.
34
72
17
433
57,633
Syv 🪐 retweeted
Blockchain needs infrastructure where privacy, identity, and compliance can coexist. That’s what Midnight is building.
35
273
17
1,634
50,477
Good news on the coming Midnight release & follow-up composability upgrade 👀 As known, the v8 release enables private contracts, with composability (v9) coming after Thanks to our great audit partners, it look like the composability upgrade (v9) will be also be this year!
20
117
18
688
35,379
Syv 🪐 retweeted
🚨SOLIDITY-AUDITOR V4 IS NOW OPEN SOURCE (MIT LICENSE) A single command now gets up to 85% recall on High severity findings from multi-week contests from last year. This used to cost protocols tens of thousands - we made it FREE, so any dev can build more safely. by PAG team🫡
50
67
22
518
45,486
Syv 🪐 retweeted
ZCode is now open source, and the reported security issues have been addressed. github.com/zai-org/ZCode We take the community’s feedback very seriously and apologize for the concern and frustration these issues have caused. We have been working closely with the ZCode team to investigate and remediate the issues raised. Independent security reviews by third-party firms are now underway. We will share the findings and provide further updates as they become available. We sincerely appreciate the developer community’s feedback and continued scrutiny. We will continue to monitor the review process closely and provide updates.
In response to the ZCode product security issues reported by the community, we have completed the necessary remediation and sincerely apologize to all our users. We have open-sourced ZCode at github.com/zai-org/ZCode, placing the code under community scrutiny and making ZCode more open and transparent. We sincerely thank the community developers who previously identified issues in ZCode. Going forward, we will establish an ongoing product security vulnerability reporting and response process. We welcome developers to continue reviewing ZCode and reporting potential issues, and we will provide rewards based on the severity of the issues reported. With respect to the code data referenced by the community, we confirm that no such data is retained and that it has never been used for model training. Following the remediation, we invited the China Academy of Information and Communications Technology (CAICT) and NSFOCUS to conduct security assessments. The results are as follows: Through its technical assessment, CAICT confirmed that the zcode-prod Alibaba Cloud OSS bucket is in a zero-data state. Security remediation has been completed in the ZCode v3.14.0 client. The Repo Wiki feature has been removed, and the workflow for generating and uploading local repository snapshots has been disabled. NSFOCUS confirmed that all data objects in the zcode-prod Alibaba Cloud OSS bucket, as well as the bucket itself, have been deleted. Remediation has been completed in the ZCode v3.14.0 client. The Repo Wiki entry point and the associated generation workflow have been removed, and no functional path capable of triggering the generation of local repository snapshots or transmitting local files externally was identified. Once again, we sincerely apologize and welcome continued scrutiny from the community. The full security assessment report will be released soon.
169
68
32
973
98,541
Syv 🪐 retweeted
Hey @Zai_org , why does ZCode silently pack entire workspaces + full .git history and upload to Aliyun OSS on login? - Server holds the only decryption key - No UI toggle to disable - Zero disclosure in privacy policy Full forensics & fix: blog.ferstar.org/en/posts/zc…
215
465
331
3,597
1,672,744
Replying to @fishy0x @immunefi
Very hard to copy my methodology and I will keep it as secret 🤫
1
2
69
BREAKING: Michael Burry says OpenAI and Anthropic's AI safety warnings are fake hype to cover for slowing growth ahead of their IPOs. "we are so awesome it could become dangerous"
316
1,259
256
10,672
487,864
Syv 🪐 retweeted
Architectural enhancements, combined with an optimized pre-training corpus, enable GLM-5.3-Flash to deliver greater intelligence with less compute.
6
34
8
1,003
157,974
Prudent institutional investors should only consider trusting a crypto-asset network after it has operated reliably for at least ten years without a hard fork. #Bitcoin
763
659
123
5,750
A note from GitHub asking to delete bitchat repositories.
22
54
5
473
42,088
Syv 🪐 retweeted
Crypto Project Shut Down 2026 - Present
301
342
169
2,221
429,609
Syv 🪐 retweeted
JUST IN: Kimi AI temporarily pauses new subscriptions after demand for Kimi K3 pushes its computing capacity near its limits.
196
304
114
4,927
643,128
The Argentine peso has lost 99.66% of its value against the dollar since 2013. $10,000 in 2013 pesos is worth $34 today.
211
415
88
4,510
401,483
Syv 🪐 retweeted
Replying to @halas_dev_
@halas_dev_ forked solidity-auditor V3 and tweaked it for Move. If this isn't the power of open-source, idk what is👏
4
2
31
600
Syv 🪐 retweeted
Privacy is no longer enough. Enterprises, institutions, and governments need confidential smart contracts, confidential state, selective disclosure, and compliance-ready infrastructure. All on a blockchain built to scale. That’s Midnight.
33
112
8
553
24,280
Syv 🪐 retweeted
hackathons are underrated as a learning tool. blogs and announcements show the happy path. building something with the tech in 48 hours shows the rough edges, the parts docs don't cover. that's where the real understanding is. the fastest way to learn a tool is still to ship something small with it.
3
3
1
36
1,882
Most documentation dies from neglect. In the last 6 months, the @MidnightNtwrk DevRel team treated docs like a product: 👉 1,900+ commits 👉 447 merged PRs 👉 64 contributors 👉 Hundreds of thousands of lines rewritten, removed, or improved The result is a faster, cleaner, and more reliable experience for developers building on Midnight. See what changed: midnight.network/blog/buildi…
11
49
3
206
25,669