🇧🇷 On October 30, the rules change for every virtual asset provider operating in Brazil. Our new report breaks down: • The SPSAV authorization deadline • Daily and monthly BCB reporting • Independent assurance • What companies need to run before they file Read the report 👇 range.org/reports/brazil-sps…

Range Riserva comes to Lisbon on 5 October, the night before @FintechMeetup @aesmonty and the Range team are hosting an evening over three wines with 40 people across fintech and stablecoins. Spots are limited. RSVP 👇 luma.com/nl90gpxt?utm_source…

Find us in Zurich next week. We'll be at CV Summit with @CV_Labs, 29-30 September. @maxrobot5, our Head of Product, is on the wallets panel: crypto holders to stablecoin payments. Wednesday, 13:15, Catalyst Stage. Going too? Reply or DM, and we'll sort a time to talk.

Eco had traction with its consumer app. Then, after FTX, its bank partners began withdrawing support one by one. @rynesaxe on the hardest decision he made: shutting it down and rebuilding @Eco as stablecoin routing infrastructure. On Range Fireside. Listen 👇

The email was real. The request was not. Revolut disclosed customer data after receiving fraudulent requests from an address on a genuine government agency domain. The communication carried valid domain authentication credentials. Days earlier, Trezor and BitBox subscribers received phishing emails through the vendors' real mailing infrastructure after a compromise at Brevo. The incidents are not connected, but the weakness is similar: the attacker did not need to spoof the channel. They accessed a channel people already trusted. That matters for payments too. A payment instruction can come from the right address, in the right thread, against a real invoice, and still be fraudulent. For stablecoins, once it settles, there may be nothing to reverse. The control cannot sit at the communication layer, because that layer is what the attacker already holds. Where it has to sit instead 👇 range.org/blog/what-happens-…

A useful test for an AI feature: can it change anything? Summarizing a dashboard speeds up retrieval, but the system is still read-only. Range Command answers questions from your treasury data and can update workspace settings on request. See it live 👇 range.org/get-in-touch?utm_s…

"Design early" @rynesaxe's advice to institutions going onchain: roughly a year of solutions engineering sits between appetite and a working use case, and the demand drivers are already in the market. @eco's advice: get product and business aligned early. If onchain payments are on your roadmap, this is worth a minute.

Without direct onboarding by the issuer, the onchain address must carry the evidence. @onrefinance is licensed to accept digital assets as collateral for writing reinsurance. Investors take that exposure through ONyc, a yield-bearing dollar asset issued on @solana that combines reinsurance premium income with collateral returns. Bought directly from OnRe, it is a regulated product backed by a KYC'd counterparty. ONyc also circulates on third-party venues, is used as collateral on @kamino and @Loopscale and is pooled on @orca_so and @Raydium. A secondary purchase on one of those venues is not an issuance by OnRe and does not give the buyer a right against OnRe. So the wallet itself needs to be assessed. Range's Risk API can screen it before it transacts, returning a risk score from 1 to 10, the reason behind it, the underlying evidence and its distance from known malicious activity. The same screen covers existing holders. For unusually large deposits, a brief hold adds a second layer, because labeling an address caught in a live exploit takes hours rather than seconds. If you are opening a permissionless entry point, screening must happen before the first purchase clears. Read the case study 👇 range.org/blog/onyc-real-tim…

Why is institutional capital still sitting offchain? Eco CEO @rynesaxe joined @range_org for a fireside and talked about the gap desks hit once they come onchain.

Every auditor asks a privacy protocol the same question: what stops a sanctioned address from getting in? Most compliance tooling in crypto assumes the transaction graph is readable. Screen the counterparty, trace the funds, flag the pattern. A privacy protocol removes that assumption by design. Once the transaction interior is confidential, that interior is no longer available to screen, and no amount of tooling reconstructs it afterward. That leaves one usable decision point, before the privacy layer applies. Assess the address and the transfer there, or do not assess them at all. That turns it into an architecture decision, with the audit as the deadline. Screening built into the program before review becomes part of the audited code. Adding it later can mean another review, a migration and months of answering diligence questions with “not yet.” @cloak_ag, private financial infrastructure on Solana, built theirs the first way. Range's Risk API runs at the perimeter of their product, inside the program that went to audit. How it works 👇 range.org/blog/how-cloak-scr…

When a dollar isn't a dollar: routing stablecoins across chains | Fireside with @rynesaxe Co-founder & CEO at @eco nitter.net/i/broadcasts/1RKjpbrgM…

🇧🇷 Filing by October 30 is only the first deadline. Then 5711 is due every business day, and 5710 is due every month. Both are sequential, so one rejected base date can block the next submission. We mapped the operating requirements 👇 range.org/reports/brazil-sps…