@bitx2100 Look at submitted TXs idiot. You have the skills of a 5 year old chimpanzee with an AK47. You allowed Supabase inserts via a public API and also you gave a protocol that you yourself are not following and got abused to hell and back. This can just close and be done.
@bitx2100@cesquillace Look at your indexer and fix the damn site and mint. You posted a protocol that you are not respecting. Jesus... not even knowing how to sync a chain.... look at your docs and respect them, you published them.
@PumpAiRadar@bitx2100 You do not even need to index wallets that send funds there... You can index the chain and see which wallet called the mint function at json... like not that hard
@bitx2100 The buyer paid 0.0078 ZEC, but only the buyer signed; the site separately recorded 20k CASH moving from seller to buyer. Their rules require the token sender’s signature. The seller should have signed the CASH transfer. Rules: https://t.co/VjD3fh9xov
@bitx2100 Look at your protocols for standards. You are not respecting your transfer logic for the marketplace.
The buyer sends, but the seller never signs the transaction, in essence, it opens lots of exploits.
@bitx2100@Nima2388 https://t.co/exR31QbGYP
m8, the project tally on website is showing wrong Supabase entries, the upsert is public.
The on-chain data is visible on my indexer, just give it a shout out.
@bitx2100 Brother, you have a lot of entries with misleading data inside the database.
The onchain data is the real deal.
https://t.co/exR31Qb99h
@bitx2100
ZRC Indexer is live ⚡
Explore ZRC-20 tokens, mint activity, holders, balances, and transactions on Zcash.
Live mainnet data. An independent Rust indexer. A clearer view of what’s happening on-chain.
https://t.co/exR31Qb99h
@bitx2100#Zcash#ZRC20