bitcoinearly

8.3K posts

bitcoinearly banner
bitcoinearly

bitcoinearly

@bitcoinearly

crypto newb

Katılım Nisan 2019
1.9K Takip Edilen198 Takipçiler
Sabitlenmiş Tweet
bitcoinearly
bitcoinearly@bitcoinearly·
@natxwang @Zeneca Cause nobody got rich eating fancy apples. Meme coins get you that shot. It’s a lottery with better odds.
GIF
English
1
1
8
1.3K
coinfoin
coinfoin@coinfoin_·
Be InfiniFi @infiniFi > Running a points program for more than 6 months > Promised TGE in December > Still running an endless points program > Basically just vault curator that launch stablecoin "ticker", nothing new > 13-week unlocking cooldown, after locking liUSD for 13 weeks, you need another 13+ weeks to unlock, with no yield Glad I only locked a small amount. Their valuation likely won’t exceed $100M Starting to fade this
coinfoin tweet media
English
13
8
24
2.2K
bitcoinearly retweetledi
DARK HIT9
DARK HIT9@HIT9crypto·
@ResolvLabs · working with law enforcement to do what exactly? They did what you allowed them to do. Retardios
English
1
1
1
589
Resolv Labs
Resolv Labs@ResolvLabs·
This notice is issued on behalf of Resolv Digital Assets Ltd. in relation to the Resolv protocol. Earlier today, a malicious actor gained unauthorized access to Resolv infrastructure through compromised private key, resulting in the minting of approximately $80M of uncollateralized USR. A full post-mortem is currently in progress and will be shared once completed. The incident was identified quickly, and the relevant smart contracts were promptly paused. Approximately 9M USR held by the attacker has since been burned in order to reduce the potential impact. The protocol currently holds approximately $141M in assets, with the only realized impact identified to date being approximately $0.5M in redemptions processed prior to the pause. Current USR supply consists of 102M pre-incident USR and approximately 71M newly and illicitly minted tokens. As an initial step in the recovery process, we are preparing to enable redemptions for all pre-incident USR, beginning with allowlisted users. The current target start date is 23 March 2026. Affected users should coordinate directly with RDAL through official channels. This incident resulted from unauthorized third-party actions, including a targeted infrastructure compromise and cyberattack. Resolv’s underlying collateral was not directly compromised. We are actively:  • tracing and seeking to contain illicitly minted USR and other affected assets  • coordinating with partners and counterparties  • working with law enforcement and onchain analytics firms to identify those responsible We will pursue all available avenues to recover assets and hold those responsible accountable. We strongly advise against trading USR or related Resolv tokens at this time while recovery measures are being implemented. Actions of users during post-exploit period may affect the recovery. Further updates regarding illicit USR, and RLP will be communicated in the near term.
English
57
30
125
45.5K
bitcoinearly retweetledi
ushouldcashout
ushouldcashout@ushouldcashout·
.@zachxbt this one has legs. Serial infra,tornado layering, prior 02/2024 operation, and a binance withdrawal that bypassed nothing.... @BinanceSecurity the tx is 0x4ece35ff, June 22 2023 18:42 UTC. You can close this today. @ResolvLabs (4/4) You're welcome!
English
1
1
2
111
ushouldcashout
ushouldcashout@ushouldcashout·
I traced the Resolv $USR exploiter's full funding chain onchain. The root wallet behind the $25M hack was seeded directly from @Binance. They have KYC on this person. Tagging @zachxbt because this rabbit hole goes deeper than just Resolv 🧵 (sorry for the tag bro) (1/4)
English
1
0
7
778
bitcoinearly
bitcoinearly@bitcoinearly·
@CrankedDegen @ResolvLabs That’s BS right there. It took long to identify and pause the contract. Question, what caused the delay? Asking in the hopes of doing better next time.
English
0
0
0
24
bitcoinearly retweetledi
The Arbing Cat
The Arbing Cat@CrankedDegen·
@ResolvLabs "The incident was identified quickly" - sure, 4 hours after the attacker kept dumping the token
English
2
1
21
1.9K
Stacy Muur
Stacy Muur@stacy_muur·
Imagine spending millions on hiring and still getting outperformed by a team of 14 people. @HyperliquidX is doing $55M revenue per employee. No funding. No marketing budget. Just a PMF. Name one project that has a more effective team.
Stacy Muur tweet media
English
34
11
132
7.3K
Behrin
Behrin@behrin·
One of the first questions we asked @Ikigaieuh are you just going to fork another large protocol He said No, and this is the reason
Ikigaieuh@Ikigaieuh

When we built Neutrl, we looked at how others in the space structured the issuance and redemption of their stablecoins. A common pattern: off-chain systems where a backend server signs orders, sets the price, and decides how much stablecoin you get for your collateral. The problem? If that server or signer key gets compromised, someone can mint millions of stablecoins out of thin air for pennies. We've seen it happen. We weren't comfortable with that. We believe well-designed smart contracts are harder to compromise than web2 infrastructure — servers get hacked, keys get leaked, infra goes down. So we went fully on-chain. When you mint NUSD, the contract queries Chainlink oracles directly at execution time, wrapped in the Euler ERC-7726 standard for additional safety checks. No backend decides your quote. No off-chain signer involved. There's no privileged role that can dictate how much NUSD gets minted for a deposit — the oracle gives the price, the contract does the math, that's it. We also don't blindly trust whatever the oracle returns. If the price of a collateral drops below a threshold we've set, the transaction reverts. We'd rather block a mint than risk giving someone a bad quote. But on-chain design alone isn't the full picture. Defense in depth matters. We use @HypernativeLabs for real-time threat monitoring — they are one of our pauser role on our contracts and can freeze operations the moment something looks off. tl;dr how we think about security at Neutrl: oracle pricing on-chain with no off-chain signers to compromise, price bounds that revert instead of giving bad quotes, per-block limits enforced in the contract, and Hypernative watching 24/7 with the ability to pause.

English
4
0
15
1.9K
bitcoinearly
bitcoinearly@bitcoinearly·
@benboymoon @behrin @Ikigaieuh @Neutrl By banning anyone who ask questions about @Neutrl points on discord. Come on Ben, stop the BS and be a man. Stop the “soon” thing. You guys are sounding like the crypto scammers that you claim you are not.
English
0
0
0
30
DarkLord_gr
DarkLord_gr@DarkLord_gr·
@bitcoinearly It's easy to not spend thousands on security until it is too late
English
1
0
1
5
bitcoinearly retweetledi
ustas.eth
ustas.eth@ustas_eth·
- be me - run tool on Resolv overnight to bug hunt - open the report in the morning - take a quick look - "all allow SERVICE_ROLE to mint an unbounded amount of protocol tokens" - "compromised settlement service can continue draining Treasury" - "SERVICE_ROLE can inflate protocol token supply" - ai slop, whatever - go make tea - open twitter What are the odds...
Resolv Labs@ResolvLabs

We are currently investigating a security incident involving unauthorized minting of USR. At this stage: The collateral pool remains fully intact. No underlying assets have been lost. The issue appears isolated to USR issuance mechanics. Our immediate priority is to: 1) Contain the incident 2) Assess impact 3) Ensure legitimate users are not affected We are actively investigating and will share more updates shortly.

English
2
1
34
6.2K