←
Reserve 🌐7,584 posts
Reserve 🌐 avatar✓

Reserve 🌐 ✓

@reserveprotocol

Reserve is pioneering onchain funds (called DTFs or Decentralized Token Funds), in pursuit of asset-backed currency. Powered by $RSR

◷ Joined May 2018▧ 1,599 Photos and videos
Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Sep 18

Every $RSR unlock now comes with a burn 🔥 This plan comes directly from the community: @AmatorPatriae proposed tying unlocking to burning, which became the design of the final Burn Gauge: no schedule, no calendar... nothing released unless the protocol has burned RSR first. If the protocol burns nothing, nothing unlocks. RSR holders choose the ratio, with five positions on the gauge: → High burn: for every 1 RSR the protocol burns, 4 more are burned from the treasury. No unlocking. → Low burn: for every 1 RSR the protocol burns, 2 more are burned from the treasury. No unlocking. → Sustain: for every 2 RSR the protocol burns, 1 is unlocked from the treasury. → Low growth: for every 1 RSR the protocol burns, 2 are unlocked from the treasury. → High growth: for every 1 RSR the protocol burns, 4 are unlocked from the treasury. At the two burn settings the treasury shrinks and nothing is released. At the three growth settings, Confusion Capital can release more than the burn-driven amount, but treasury RSR is burned in exchange at that position’s ratio. An unofficial burn gauge simulator is available here: claude.ai/artifact/5UAT2smqK… @nnevvinn, Confusion Capital, ABC Labs, Best Friend Finance and every company Confusion Capital incubates sit these votes out; they won’t vote with the RSR they hold. The gauge is set by the RSR holder base. The community will vote on it every quarter by ranked choice, following the quarterly update call and report, so you can see where the business stands before choosing a setting. The first gauge vote is open now and runs seven days ↓ snapshot.box/#/s:reserveprot…

Post attachment
Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·14h

RSR withdrawals are open again on Binance. Binance's team confirmed this to us directly, and RSR now shows "Normal" for both deposits and withdrawals on Binance's status page: binance.com/en/network We expect this to be our final update on the Binance exploit that resulted in stolen RSR. Binance's update below covers its wider recovery from the Oct 29 hack. RSR withdrawals reopened after it went out, so it doesn't mention RSR. Quick recap for anyone catching up: • On Oct 29, an attacker took ~3.38B RSR from a Binance hot wallet and sold it onchain that night. • The RSR token and Reserve's contracts were not affected. RSR held outside Binance was never at risk. • Binance committed to covering all losses from the hack with its own funds. What this means for you: • If you hold RSR on Binance, you can withdraw it normally again. • Binance's proof-of-reserves page shows which tokens its latest snapshot covers, if you want to verify your balance. • If you hold RSR in your own wallet, nothing changes. Only use the official Binance website, and ignore anyone offering RSR "refunds," migrations or airdrops. Thanks to the Binance team for keeping us informed throughout.

Post attachmentPost attachment
Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Nov 7

One hour ago, FinCEN announced an order “effectively cutting off MEXC Global’s access to the U.S. financial system for facilitating at least $16 billion in illicit transactions, including activity connected to Iran sanctions evasion.” In response to this order, Reserve and its market making partners are pausing liquidity provision for $LCAP and $CMC20 on MEXC and will withdraw liquidity provision funds shortly. Liquidity for these tokens on other venues including onchain and on app.reserve.org remains unaffected.

Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Nov 3

Update for RSR holders on Binance's recovery from the Oct 29 hack: Quick recap: along with many other coins and tokens, an attacker took ~3.38B RSR from a Binance hot wallet on Oct 29 and sold it onchain that night. The RSR token and Reserve's contracts were not affected, and RSR held outside Binance was never at risk. What Binance announced today: • It has replaced about 95% of the stolen assets, by value, with its own funds. • Balances in 10 tokens (BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC) are now proven to be backed at least 1:1. Users holding those tokens can check this themselves with Binance's proof-of-reserves tool. • The remaining ~5% are less-liquid tokens outside those ten, which take longer to buy at the size needed. Binance says it's continuing to acquire them. What this means for RSR: • RSR is not one of the ten verified tokens, so RSR balances on Binance can't be independently verified yet. RSR is part of the remaining 5% Binance says it is still acquiring. • Binance plans a new proof-of-reserves snapshot covering more tokens on Nov 4. The proof takes about 40–50 hours to generate, so results should follow around Nov 6. • Binance is reopening withdrawals in phases, with the next phase starting tomorrow. It hasn't said yet when RSR withdrawals will resume. If you hold RSR on Binance, follow Binance's official announcements and only use the official Binance website. If you hold RSR in your own wallet, nothing has changed and there's nothing you need to do.

Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Oct 30

Update on the Binance exploit and RSR: Binance confirmed the attacker drained one of its hot wallets and that it will cover all losses with company funds, including the stolen RSR. We've been in direct contact with Binance's team since our last update, and they've moved quickly and responsibly, confirming that they will be re-purchasing the missing 3.38B RSR promptly. New from Binance co-CEO @_RichardTeng's video update: • Binance has set aside over $6.34B of company funds to cover the stolen assets. About $5B of that is already held in the exact tokens affected (he named USDC, USDT, BTC, ETH and BNB). • It's buying the remaining assets through market and OTC channels. Because the Reserve treasury does not have an appetite to reduce its RSR position, in the case of RSR we believe Binance will acquire on the open market through a professional market maker. • Binance withdrawals are paused while the team rebuilds and retests its withdrawal system. It hopes to reopen them before Sunday. Until then, RSR on Binance can't be withdrawn. • A full proof-of-reserves report has been promised by Monday. That's where you'll be able to check that RSR balances are fully backed. We infer from this that the RSR re-purchase will be completed by Monday. • Binance is working with law enforcement, blockchain analytics firms, token issuers and other exchanges to trace and recover the stolen funds. On Reserve's side, nothing has changed since our last update. We'll keep monitoring and share more as Binance does.

4:41
Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Oct 30

Update on the Binance hot wallet exploit and RSR: The stolen RSR has been sold, Reserve’s contracts were not affected, and RSR holders don’t need to do anything. If you held RSR on Binance, follow @binance’s updates. They’ve said “Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.” We take this to indicate they intend to re-purchase all assets lost in the exploit, including 3.38B RSR, to make their users whole. However, we have not been briefed on the specifics of how Binance intends to cover losses and have not done any of our own financial analysis of Binance’s ability to absorb this loss. The attacker took 3.38B RSR from Binance. Between 8:53 and 9:08 PM ET on Oct 29, they swapped all of it on Uniswap v3 for 1,856 ETH ($4.1M). As far as we can see onchain, they no longer hold any RSR, though it remains possible that the onchain swaps included wash trades with obscured attacker-funded wallets. See: etherscan.io/token/0x320623b… Before the sale, we pulled Reserve treasury-provided onchain liquidity so it couldn’t serve as the attacker’s exit. It appears that arbitrage bots and other traders bought the RSR instead. RSR is immutable with no admin keys, so no one, including us, can freeze it. The RSR token and Reserve protocol contracts were not affected. Since the attacker apparently no longer holds RSR, we believe it can’t be used in bulk against Reserve DTF governance. We are continuing to monitor the situation for any potential cascading effects of so many tokens being stolen and sold at once. For now we do not see any cause for pausing any Reserve products, so everything remains in normal operation.

Post attachment
Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Oct 29

We’re aware of the suspected Binance hot-wallet exploit, which appears to include ~3.4B RSR. The RSR token and Reserve protocol contracts are not affected; this is an exchange custody incident. RSR is immutable with no admin keys, so no one, including us, can freeze it. We’re working with Binance, market makers, and exchanges to flag the attacker’s addresses, and monitoring RToken/DTF governance. For your Binance account, follow Binance’s updates. According to CZ, user funds are not at risk, indicating Binance will cover any losses. As a precaution, we’ve temporarily withdrawn Reserve-provided onchain RSR liquidity so the stolen RSR can’t be sold into it. Third-party LPs in RSR pools should consider doing the same.

Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Oct 2

Our Q3 report will cover platform metrics, revenue, $RSR burn, and treasury activity, and company strategy Have a question you want answered on the call? Reply here or send it in TG by October 13 and we’ll work it into the presentation! Call will be recorded, as always!

Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Sep 25

The results are in, and suddenly it feels really hot in here... ethereum:0x320623b8e4ff03373931769a31fc52a4e78b5d70

Post attachmentPost attachment
Snapshot avatar
⟳ Reserve 🌐 retweeted
Snapshot@SnapshotLabs·Sep 25

@reserveprotocol is voting to set the opening position of its new Burn Gauge, a five-way dial ranging from burning 4 treasury $RSR for every 1 the protocol burns, to unlocking 4. Holders adopted the gauge on September 17th. It only acts when platform fees on mints and total value locked market-buy RSR and burn it: "Nothing unlocks unless that burn is happening." Confusion Capital and ABC Labs, which would receive growth-setting unlocks, are sitting out, along with @nnevvinn, who drafted the original settings, and @bffcalifornia. The rest of the holder base sets the dial. Per @raphbaph's recap, Nevin argues for High burn, the setting that unlocks nothing: the treasury doesn't need more RSR unlocked soon, holders want burns, and the revenue stream that causes burning is moderate, so High burn won't cost the treasury much. Voters rank all five settings by preference, lowest eliminated until one has a majority. Ballots stay encrypted until close, so no setting can be read as leading. 68 wallets have cast 1.05B RSR so far, clearing the 1B RSR quorum at 105.3%. Voting closes September 25th at 4pm UTC. Proposal: snapshot.box/#/s:reserveprot…

Post attachment
Reserve 🌐 avatar
Reserve 🌐@reserveprotocol·Sep 22

Welcome! We’ve been providing portfolios on @base for years! Good to have you 🫡 base:0xcef8db49e456f872e288e1c042f916e9ced7c781 looks good here btw

Post attachment