WOW, El ratio de perfiles creados / cartera sigue descendiendo. Ya estamos en 1.31 lo que sigue confirmando que nuevas personas están entrando.
El próximo objetivo será alcanzar las 2700 wallets que confirmarán que el 10% de los holders de #CAW están interactuando con la TESTNET.
Many memecoins have people hyping them on X. But CAW has code repositories, an SDK, a working frontend, and a live testnet. That means real technical builders are behind it. You don’t maintain and develop infrastructure like this for 3–4 years with marketing alone.
CAW has 26,949 holders.
Gilgamesh’s testsite reports 2,281 total users, 958 active users this week, and a likely cawNAME supply around 2,282.
That is about 8.5% of CAW holders as total test users and about 3.6% as weekly active users.
So I cannot confuse a small testnet crowd with cawmmunity acceptance.
A small user base cannot be marketed as if it is cawmmunity accepted.
Cleary so far it is not and this is being noticed even by gilgamesh own propagandists.
The manifesto already gave the standard:
“2. It is strongly recommended that a peer group is formed to develop and review smart contracts.”
It also warned why:
“as there is no leader in this process, all types will attempt to claim ownership of the process.”
And it warned about the exact builder archetype now being defended:
“there will those everso helpful who claim to be able to ‘do it all’ but will write the perfect code with the perfect backdoor.”
The standard ends clearly:
“Only a cawmmunity reviewed and accepted contract on a public github will be acceptable.”
That is the bar.
Pre-peer-review probes already show compatibility problems with the manifesto standard: the likely cawNAME contract candidate still reports owner 0xf71338f3eaa483aa66125598b09ba1988e694a95; independent historical rebuild proof is still missing until a clean empty-DB rebuild produces deterministic export hashes; LayerZero trust/config assumptions still need to be closed or replaced, not waved away; and renouncing one owner address does not prove decentralization if the architecture still depends on one builder’s stack, default frontend, indexer, operator path, or cross-chain trust layer.
Gilgamesh has acknowledged some points, including that hashes should be public and that this is testnet. Fine. Acknowledgement is not proof nor does it make it decentralized.
The proof pack is simple:
CAW holders: 26,949
testsite totalUsers: 2,281
activeUsersThisWeek: 958
likely cawNAME supply: 2,282
likely cawNAME owner: 0xf71338f3eaa483aa66125598b09ba1988e694a95
Missing proof:
cawmmunity acceptance
completed peer review before launch
verified deployed bytecode matching reviewed source
independent empty-DB historical rebuild with matching export hashes
closed admin/key surface
LayerZero trust/config removal or hard proof of neutralization
a protocol path that cannot be shaped by one builder, one frontend, one indexer, or one operator stack
CAW was not made for a builder to claim ownership of the process.
CAW was made for the cawmmunity to review, accept, and deploy what is truly decentralized.
#CAW
Last night I pushed a bunch of code to github.
https://t.co/jyTvMicKYq
This includes major steps towards finishing the protocol, the front end, and all the infrastructure needed to support a fully feature complete app.
We are extremely close.
The crow will fly.
$CAW 🌙
$CAW has been till this day the biggest conviction project for me
No VC, no team ... just pure vision from @RyoshiResearch and us community whom is his believers
And @caw_dev, the man who actual put in the time and effort to fulfill the manifesto! Respect
Our time will come
Lots of testing, almost everyday
Also I notice different contract has been created, which might stand for update code OR different function contract
Anyway, progress is being made
#CAW $CAW @caw_dev