@RSync25
Account based inSouth America!
About this account
- Account based in
- South America
- Connected via
- South America App Store
X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
₿itcoiner, Mid-level Engineer & Building AI & Robotic Labs #npub1c8l997847szpt6prwug6usmfl48v7afun9d4zt6f5xexhrdps45sctmg0w
World
Joined July 2016
- Tweets124K
- Following5.5K
- Followers4.4K
- Likes197K
Pinned Tweet
In the next 10 years you’ll need to know how works with AI, robotic and computer quantum. Everything will work together
R-Sync 同期🦀🗿 retweeted
I'm seeing a lot of freshly made accounts or BIP110 accounts complaining about having their funds stuck in Liquid. While it is possible that some Liquid users (like traders) have large amounts of L-BTC they cannot peg out yet, real AQUA users should not be "stuck," since Liquid-to-Lightning swaps via Indra are operational.
Moreover, we have disabled reverse swaps (Lightning to Liquid), so no AQUA users will receive L-BTC from Lightning. This is to make sure they do not accumulate L-BTC until peg operations are fully restored.
AQUA clearly labels the L2 Bitcoin account as a spending wallet, which should hold whatever you intend to spend in the near term (small amounts, like what you would keep in ecash or WoS), not your life savings.
Restoring full Liquid functionality is squarely on Blockstream's shoulders, as they are the technical service provider for the network. I believe another update should be coming soon. JAN3/AQUA can only support our users while the work is being done.
R-Sync 同期🦀🗿 retweeted
CORRECTION: RIVER SUES INDEPENDENT MINING ENTITY OVER $6.7 MILLION PAYMENT AGREEMENT, NOT BLOCKSTREAM CORP.
Blockstream Mining (Blockstream Services Canada ULC) was spun out of Blockstream in early 2025 and now operates as an independent company.
It continues to use the Blockstream Mining brand under a licensing arrangement.
The lawsuit names Blockstream Services Canada ULC as the defendant, not Blockstream Corporation.
RIVER SUES BLOCKSTREAM OVER $6.7 MILLION PAYMENT AGREEMENT
River Financial has sued Blockstream Services Canada, alleging breach of contract over a termination agreement requiring Blockstream to pay River roughly $6.7 million.
The agreement included $3.55 million in prepaid refunds and a $3.15 million early termination payment.
R-Sync 同期🦀🗿 retweeted
Since mid-2024, Blockstream Services USA and Blockstream Services Canada have not been under the ownership, control, or management of Blockstream Corp. The businesses were spun out as part of the Blockstream Mining business and have since operated as separate companies, with no shared equity ownership or management with Blockstream Corp.
Following the separation, they retained the Blockstream name for a limited period under a brand licensing agreement.
R-Sync 同期🦀🗿 retweeted
RIVER SUES BLOCKSTREAM OVER $6.7 MILLION PAYMENT AGREEMENT
River Financial has sued Blockstream Services Canada, alleging breach of contract over a termination agreement requiring Blockstream to pay River roughly $6.7 million.
The agreement included $3.55 million in prepaid refunds and a $3.15 million early termination payment.
Trezor
C-lightning
Boltz
Btcpayserver
Pocket Bitcoin
Liquid
Getalby
Trezor
Bitbox
Revolut
Swiss Bitcoin Pay
Blink
Bitget
At 18:31 UTC on September 24, 2026, Bitget’s security systems identified unauthorized transfers involving a limited number of hot wallets.
Our security team immediately activated emergency response procedures and began a full investigation.
Based on our current assessment, approximately $351.6 million in assets were affected. Bitget’s cold wallets and the overwhelming majority of platform assets remain secure and unaffected.
Most importantly, user funds remain protected.
The incident falls within the coverage of Bitget’s User Protection Fund, which currently holds more than $464 million.
Customer account balances remain accurate, and deposits and trading continue to operate normally.
As a precaution, withdrawals have been temporarily suspended while our teams complete a comprehensive security review.
We have identified and flagged the relevant transfer addresses and have formally engaged law enforcement agencies and leading on-chain security partners.
We are working around the clock to restore withdrawal services as soon as it is safe to do so.
Bitget will provide further updates through our official channels.
We will not speculate on the attack vector while the investigation remains ongoing. Our focus is on protecting users, securing all systems, and delivering complete transparency throughout this process.
R-Sync 同期🦀🗿 retweeted
🇨🇭 SWITZERLAND PLANS NEW CYBERSECURITY LAW ADDRESSING OPEN-SOURCE SOFTWARE
The Swiss Federal Council is moving to create a standalone federal cybersecurity law, explicitly citing open-source software as an area that could receive a more comprehensive regulatory approach.
The law would consolidate rules covering software and hardware security, critical digital data, cloud and hosting providers, and cyberattack reporting.
It would also establish binding requirements for manufacturers, importers and distributors, including market surveillance and the ability to ban sales of insecure products.
A consultation draft is due by June 2027.
To strengthen Switzerland's cybersecurity, the government has tasked the defence department with drafting a new federal act regulating digital products, data and infrastructure. The law will be based on the European Cyber Resilience Act. admin.ch/de/newnsb/zX9oNK8tu… @vbs_ddps
R-Sync 同期🦀🗿 retweeted
AI RESEARCH SHOWS ONLINE PSEUDONYMS MAY NO LONGER PROVIDE ANONYMITY
Research published at USENIX Security 2026 shows LLMs can deanonymize pseudonymous internet users at scale by analyzing their posts and matching them across platforms.
Researchers say successful identifications cost as little as $1–$4 each, while using higher-reasoning AI models doubled their matching success rate.
The team warns that as AI improves, deanonymization will become cheaper and more effective, potentially forcing platforms to rethink what online anonymity actually means.
R-Sync 同期🦀🗿 retweeted
BITGET FACES POSSIBLE $176 MILLION HACK
On-chain data shows $176 million in ETH and USDT0 moved from multiple Bitget wallets to a single address amid suspected unauthorized activity.
No Bitcoin was involved in the suspected hack.
Bitget has yet to comment.
Looks like Bitget just got hacked for $178M
follow the hacker's fund flow here
arkm.com/explorer/entity/f22…
R-Sync 同期🦀🗿 retweeted
Every account affected by the September 19 incident has been made whole.
We restored each account to its exact pre-incident balance.
Affected users were notified directly before this post.
Thank you to our mission-aligned shareholders who stepped in.
R-Sync 同期🦀🗿 retweeted
⚠️Cake Wallet's Yesenia Gonzalez's Telegram account was hacked and the account is now attempting to convince people to install malware
Cake knew about this for over a week, but made NO PUBLIC WARNING
Multiple of Cake's partners are already affected
R-Sync 同期🦀🗿 retweeted
Liquid BTC is governed by 15+ bitcoin companies. Are you telling me that between all of them they cannot come up with 600 BTC to keep the business going?
R-Sync 同期🦀🗿 retweeted
Based. @Liquid_BTC needs to restore 1:1 peg, not by issuing a sh*tcoin but by adding missing 600 BTC. Allowing users accumulate more unbacked L-BTC is irresponsible. Imo, no other way to survive this (the longer it takes the more likely users/companies won't trust them anymore).
We know many of you are eager to know what will happen to Lightning payments in the BULL wallet, and when you will be able to convert L-BTC to BTC.
The reality is that the Liquid network's situation is completely outside of BULL’s control: we have to wait for the Federation to resume pegouts.
Any service that accepts L-BTC to send out BTC will soon accumulate L-BTC in its inventory, while its BTC inventory is depleted. Under normal circumstances, swap services that accumulate L-BTC use the pegout mechanism to rebalance their inventory. Absent this mechanism, our view is that a swap provider or exchange cannot operate sustainably.
BULL could re-enable inbound Lightning payments, allowing users to start accumulating L-BTC again, which would provide liquidity for those who want to exit L-BTC.
We have decided not to follow this approach for now and will wait for pegouts to resume, because that approach would rely on some users taking the risk of holding L-BTC without compensation or a guarantee that they can exit back to BTC.
For the pegout mechanism to be reactivated in Liquid, two conditions must be met.
First, the software needs to be secure to avoid another exploit that could drain the federation’s remaining ~3,600 BTC. That part is within the control of the federation members and their IT provider, Blockstream. The known vulnerabilities, as far as we know, have been fixed. What is harder is finding any currently unknown vulnerabilities, but this should not prevent the Liquid network from moving forward.
The second and most serious problem is that the total amount of BTC held by the federation must be equal to the total amount of L-BTC in circulation. In other words, the backing of L-BTC by BTC must return to a 1:1 ratio. We are aware of ongoing efforts to 'fill the gap' and at this stage, all we can do is wait for that to happen. Once that is done, BULL will be able to offer a conversion service that allows users to exchange their L-BTC for BTC at a 1:1 exchange rate.
Based on the information we have, our expectation is that Liquid swap and exchange services allowing users to convert their L-BTC to BTC could resume within 30 days. This is an educated guess, not a guarantee.
Looking beyond the current situation, we are also evaluating the best path forward for Lightning payments in the BULL wallet. As part of BULL’s ongoing R&D efforts, our CEO, @francispouliot_ is preparing a presentation examining the tradeoffs of the main alternative payment protocols available to Bitcoin wallets.
The goal is to identify the most robust and sustainable architecture for providing BULL users with the best possible experience going forward.
We would like to thank all our users for their continued patience and understanding. We will share further updates as reliable information becomes available.
R-Sync 同期🦀🗿 retweeted
We know many of you are eager to know what will happen to Lightning payments in the BULL wallet, and when you will be able to convert L-BTC to BTC.
The reality is that the Liquid network's situation is completely outside of BULL’s control: we have to wait for the Federation to resume pegouts.
Any service that accepts L-BTC to send out BTC will soon accumulate L-BTC in its inventory, while its BTC inventory is depleted. Under normal circumstances, swap services that accumulate L-BTC use the pegout mechanism to rebalance their inventory. Absent this mechanism, our view is that a swap provider or exchange cannot operate sustainably.
BULL could re-enable inbound Lightning payments, allowing users to start accumulating L-BTC again, which would provide liquidity for those who want to exit L-BTC.
We have decided not to follow this approach for now and will wait for pegouts to resume, because that approach would rely on some users taking the risk of holding L-BTC without compensation or a guarantee that they can exit back to BTC.
For the pegout mechanism to be reactivated in Liquid, two conditions must be met.
First, the software needs to be secure to avoid another exploit that could drain the federation’s remaining ~3,600 BTC. That part is within the control of the federation members and their IT provider, Blockstream. The known vulnerabilities, as far as we know, have been fixed. What is harder is finding any currently unknown vulnerabilities, but this should not prevent the Liquid network from moving forward.
The second and most serious problem is that the total amount of BTC held by the federation must be equal to the total amount of L-BTC in circulation. In other words, the backing of L-BTC by BTC must return to a 1:1 ratio. We are aware of ongoing efforts to 'fill the gap' and at this stage, all we can do is wait for that to happen. Once that is done, BULL will be able to offer a conversion service that allows users to exchange their L-BTC for BTC at a 1:1 exchange rate.
Based on the information we have, our expectation is that Liquid swap and exchange services allowing users to convert their L-BTC to BTC could resume within 30 days. This is an educated guess, not a guarantee.
Looking beyond the current situation, we are also evaluating the best path forward for Lightning payments in the BULL wallet. As part of BULL’s ongoing R&D efforts, our CEO, @francispouliot_ is preparing a presentation examining the tradeoffs of the main alternative payment protocols available to Bitcoin wallets.
The goal is to identify the most robust and sustainable architecture for providing BULL users with the best possible experience going forward.
We would like to thank all our users for their continued patience and understanding. We will share further updates as reliable information becomes available.
Liquid update for BULL Wallet users
The Liquid Network has been resumed, producing blocks and processing transactions again.
However, Swaps from L-BTC to BTC and L-BTC to LN remain unavailable until the 1:1 peg is fully restored and peg-out operations are allowed again.
BULL’s default receiving wallet, aka Secure Bitcoin Wallet, which uses the Bitcoin network for transactions, is unaffected by this incident.
BULL’s instant payments wallets use the Liquid Network. While it is now possible for users to receive payments via Liquid, we strongly discourage them from doing so.
The BULL wallet automatically prevents users from accumulating more than 1,000,000 sats in their wallet via its autoswap feature, which is enabled by default.
While we wait for the Liquid Network peg to return to its full 1:1 reserve, this feature is not functional.
What’s next
We are confident the 1:1 peg will be restored and that no BULL Wallet user will lose funds as a result of this incident. Once full backing and peg operations are restored, you will be able to convert your L-BTC to BTC or to LN as before.
If full backing cannot be restored, we will advocate on behalf of our users for a recovery plan that lets every affected user recover funds proportional to the peg ratio.
BULL’s primary directive is, and always has been, to make Bitcoin a useful, private and censorship resistant means of exchange. Only then can our Mission to Destroy Fiat be realizable.
BULL first integrated Lightning in its exchange in 2018. Since then, we have kept up with all new developments in the space, examined all available alternatives and tradeoffs in depth. We have presented on this topic at technical conferences, and we plan on soon releasing more insights into our approach.
We thank our amazing users for their patience and support.
Despite the difficult cybersecurity incidents of the past few months, we remain dedicated to building infrastructure to make Bitcoin a scalable and usable form of money.
R-Sync 同期🦀🗿 retweeted
We have published the technical security assessment of the September 6 Liquid incident, which details the root cause and mechanics of the exploit, an incident timeline, and the engineering and security changes being implemented in response.
blog.blockstream.com/liquid-…
R-Sync 同期🦀🗿 retweeted
🟢Swiss Bitcoin Pay is back online.
First, the essentials: no funds were lost. That includes merchant balances awaiting onchain settlement, which are fully intact, and cards balances. All amounts owed didn't moved.
As stated on Monday, we continue to assume that customer email addresses, Bitcoin addresses, IBANs, transaction history and hashed passwords may have been accessed. We are treating that data as compromised.
We can now add one finding: we found no evidence that identity or KYC/KYB documents (that some of our customers had chosen to provide) were extracted. Every attempt we traced to copy files out to the attacker's server failed. We want to be precise: no evidence is not the same as a guarantee. This is what our deep investigation found, and we will tell you if that ever changes.
We have closed the vulnerability, rotated every credential, and drastically hardened our infrastructure.
One thing we want to be open about: we had been working for months on a new infrastructure and modern stack, built to a far higher security standard. It was scheduled to go live this week. A few days earlier, and this attack would not have been possible. We are not saying this as an excuse: the system that was breached was ours, and so is the responsibility. We are saying it because you deserve the full picture, not a curated one.
What we recommend: change your password, and change it anywhere you reused it (or use a password manager). Be sceptical of any message about this incident, even one that already knows your details: with an email, an IBAN and a transaction history, phishing gets convincing. We will never contact you asking for a password, a seed phrase, or to move funds.
Thank you for your patience this week. We took the time to do this properly.
We're back, and stronger.
R-Sync 同期🦀🗿 retweeted
AML is gay and retarded. If a company is forced to stop accepting valid Bitcoin transactions, and still wants to operate, they have to say so to users. "Sorry, dear users, your UX will be worse because external malicious actors are forcing us to refuse some valid Bitcoin transactions. We don't want to stop serving you altogether, please bear with us while we try to minimize the damage." The worst idea is to try to gaslight users by spinning the above as "Good news, dear users, as a security improvement we are gifting you this scoring so you don't end up whit evil tainted coins!". This is a similar issue to @wasabiwallet's blacklist communication disaster.
R-Sync 同期🦀🗿 retweeted
Blink services are back online. The vulnerability behind the incident has been fixed and verified, and access has been restored for all unaffected accounts. If your account was not affected, you can continue as usual.
Accounts of affected users will remain locked temporarily.
Non-custodial balances were never affected.
A full post-mortem will follow. Thank you for your patience.
Questions? Reach us at [email protected].
Update: A few dozen custodial accounts were affected by the incident.
Every affected account is identified and will be made whole.
If you were affected, there's nothing you need to do.
If you have questions, reach out at [email protected] any time.
Non-custodial balances are unaffected.