TLDR: I propose to create a new Radix Website from scratch, new Design + Structure to merge into one several pages/subdomains, etc. that we have all over, are outdated and maybe too expensive to maintain.
———–
Looking at all the current handover assets from Foundation to Community, a big part of it is the Radix Website, Blog, Documentation, Wallet + Dev Hub pages… mainly static pages designed for information and marketing.
Instead of just migrating these pages to a new hosting and wasting energy, I would keep the current Webflow subscription until August 2026 (250/mo), as Adam proposed. Just hand over the account ownership to the DAO or close it completely then.
In the meanwhile work should start already to build the new revamped website, with feedback from community and to follow our new needs. The revamped website can be built with something more open source and self hosting options if needed, so in emergencies like we have now, can be backed easily and moved.
I had in mind Astro+Cloudflare pages, as costs are nearly zero for hosting on Cloudflare. If we want to add more functionality we can hook up also a CMS but then we will pay some monthly fees.
In terms of costs these are mainly for the work done on redesigning from scratch and giving some sort of new face to Radix, which i think is needed sooner or later regardless.
Now this new website you can do:
on the cheap with some boilerplate framework if you just want the message through, but then you look cheap.
with better design and structuring, rethinking the flows, regroup, etc. …will cost a couple of thousands.
I could do both ways but honestly I’d go for the second because we can start building momentum for the Xian/Hyperscale RS upgrade. This needs to be done in advance, not post launch.
I’m working on a web project that I’d like to propose as the official Radix website, with the goal of having the entire community help complete it and get it fully operational.
It’s currently in beta and still has some bugs. The documentation, blog, forum, games, and transparency sections use placeholder data just to showcase the design, but the plan is to implement real data via a database. The Dashboard is real, though wallet connection isn’t enabled yet.
You can check out the live site here—I’d love to hear your thoughts and feedback:
https://radix-community.genkipool.com
I’ve also included the GitHub link if anyone wants to contribute. Your help would be greatly appreciated, as I’m developing this on my own, without paid AI, and with limited time:
https://github.com/genkipool/Radix_Community
I hope you like it! Any comments or suggestions are more than welcome.
this network, which is considered dead, instead produces so much material that I myself cannot keep up with it. I would say this site is excellent and now I will try to look at it better
about this “Over $3.8B stolen in DeFi hacks in 2022.” I instead would point out the latest hacks ‘280M usd Drift and 290M usd Kelp’.
and here
"Native MiCA, DORA and AML Compliance
Auth Zones allow restricting asset holding to wallets with verified KYC (idOS). Travel Rule and AML are implemented at the base layer, not in external middleware."
do you know the MiCA, DORA and AML Compliance ?
this compliance rules will be satisfied by verifying KYC using idOS ?
It Is the same I think, but I don’t know this compliance rules in details
and also here:
ROA, it stands for Radix Engine ? I usually look at it as RE
and here:
what do you mean here with ‘Native Smart Accounts’ ?
Institutional Multisig Without Smart Contracts
Native Smart Accounts with 2-of-3 or N-of-M rules for corporate treasuries.
Hi! Thank you so much for taking the time to analyze the website so thoroughly; your feedback is super helpful. I’ll answer you point by point:
1. About the hacks:
You are absolutely right! I’ve already removed the 2022 part and added the Drift and Kelp hacks from 2026. This makes it look much more up-to-date and gives it more impact. Good catch!
2. About MiCA, DORA, AML, and idOS:
To be honest, I’m no financial or legal expert, but according to the research I’ve been doing with the help of AI, it works like this: idOS specifically solves the KYC and AML part (meaning, identifying who the client is and preventing money laundering). On the other hand, MiCA and DORA are broader European regulations that demand, on top of the above, high cybersecurity standards to prevent hacks.
The idea I’m trying to convey here is that, by combining Radix’s default anti-bug security with the identity verification provided by idOS, companies can comply with this whole package of European laws directly on the network, without relying on clunky third-party patches.
3. ROA or RE?
They go hand in hand, but they are not the same. ROA (Resource-Oriented Architecture) is the theory and the design: the concept that on Radix, tokens act like “physical objects” that cannot be duplicated or lost due to a coding error. The RE (Radix Engine) is the engine or the machine that makes that idea work.
4. What are “Native Smart Accounts” and the 2-of-3 thing?
I’ll split it into two parts so it’s clearer what we are talking about:
Native Smart Accounts: On networks like Ethereum, a normal account is “dumb” (it only sends and receives). If you want the account to do advanced things, you have to program a custom Smart Contract and cross your fingers that nobody hacks it. On Radix, all accounts are already “smart” out of the box (native). They come with advanced features built into the protocol itself, so you don’t have to code or invent anything external.
2-of-3 or N-of-M rules (Multisig): This is simply one of the features of those accounts. It’s used so a company can set up its treasury and say: “To move funds, we need the signature of 2 out of our 3 directors”. Since the Radix account is already smart by default, you can configure this multisig rule super securely without needing to rely on complex third-party Smart Contracts.
I hope this clears things up! Let me know if you spot anything else on the website, I really appreciate your help.
