rex retweeted
From the streets to the markets, from the Cyclists' Park to the heart of Uyo!
We took GAMDOM beyond the screen and straight to the people of Akwa Ibom! The energy, the love, the smiles, and the excitement were on another level! ❤️
Flyers in the air, smiles everywhere, and one name echoing through the streets… GAMDOM!
This is more than just a crypto casino platform. GAMDOM IS A MOVEMENT!
And trust me, this journey is only getting started.
More cities, more faces, and more unforgettable moments!
GAMDOM is the platform. STEVE is the code! 💚
Uyo showed up, and the love was REAL! ❤️
We love @gamdom
we love @stevewilldoit
#Gamdom100kRound2
rex retweeted
the @FungoLabs genesis nft mint goes live tomorrow and it’s going to be a bidding process.
here’s how it works 👇
there are 3,000 nfts up for grabs:
- 500 free mints for whitelist holders
- 2,500 through a sealed-bid auction
so, what is a sealed-bid auction?
think of it as putting your offer in a closed envelope. nobody gets to see what others are bidding.
you’ll bid in cZAMA (zama’s encrypted token) and choose two things:
- how much you’re willing to pay per nft
- how many nfts you want
others can only see that you placed a bid, when you placed it, and the number of bids. your actual offer stays hidden.
how is the final price decided?
once the auction ends, all bids are revealed and ranked from highest to lowest.
the bid that fills the 2,500th nft sets the final price.
everyone who wins pays the same price, and any extra cZAMA is refunded.
what happens to your bid?
- bid above the final price: you get all the nfts you requested.
- bid at the final price: you share the remaining nfts based on how much everyone requested.
- bid below the final price: you get nothing, and your cZAMA is returned.
a few things to know before bidding:
- bids are binding. you can’t cancel them.
- each bid comes with a small, non-refundable encryption fee.
- if demand is below 2,500 nfts, everyone pays the lowest bid price.
- nfts are minted sealed, and you decide who gets to see what’s inside.
- each nft holders get 1,113,861 $FUNGO token at TGE.
that’s pretty much everything you need to know before the mint.
goodluck boys !
rex retweeted
A dream within a Dream.
my entry for #Gamdom100kRound2
don't stay poor, bet on @gamdom [use code STEVE]
tags: @stevewilldoit @kingadukes
username: theprocess92
rex retweeted
Halloween at TestSprite. Some of us REALLY dressed up. 🎃
Office costumes, a night at Northwest Trek’s Hoot ’n’ Howl, and plenty of laughs.
Proud of what we’re building. Even happier we get to build it with this crew. Here’s to what’s next. 💚
rex retweeted
imagine doing it all in one app.
- you can receive, send and withdraw crypto
- you can receive, send and withdraw fiat to any local bank of your choice
- you can buy and sell gift cards
- pay your bills: buy data, electricity bills, fund your betting platforms
- create a virtual dollar card for international payments
that’s where @getparagonapp steps in, with little to no charges at all and the best rates out there, you can even negotiate for rates !
- download the Paragon app 👉 onelink.to/
- sign up use my code: ALTBRIGHT_
5k each for the first 3 people to sign up using my code and follow @getparagonapp
rex retweeted
it’s a new month and i needed to sort some bills today
used @getparagonapp to convert my crypto to naira, app was fast and seamless
i’ve been using paragon app to convert my crypto to Naira, and the experience has been really smooth.
The process is pretty straightforward:
➙ download the Paragon app 👉 onelink.to/qnzrub
➙ use my code: YVNGJAY
➙ fund your wallet with crypto
➙ your funds are automatically converted to Naira.
you can download the app, set up your account, and give it a try whenever you’re ready.
Definitely worth checking out. 🤝
rex retweeted
Second slide is so fucking sad.
Scammers don't have conscience, because that message was bad. Very bad and see what he replied with.
Y'all deserve the absolute worst things life can throw at a person.
rex retweeted
put a lot of work into this
excited for what is to come
kindly check it out guys 🫶
Software is how money moves today, from SaaS subscriptions and API micro-billing to automated payroll and autonomous AI agents buying compute on demand.
Every standard payment leaves a metadata footprint detailing who paid, how much, and how often.
Python handles a massive portion of this financial infrastructure, but developers have never had a simple, native way to process private payments.
ZecPy solves this.
By running pip install zecpy, any Python backend, script, or AI agent can send and receive shielded Zcash in just a few lines of code.
It handles key tasks out of the box: issuing unique private addresses for every invoice, managing bulk payouts to dozens of recipients in a single transaction, supporting cold-storage offline signing, and setting hard budget caps for autonomous agents. Under the hood, it relies directly on Zcash's official Rust cryptography (librustzcash).
Privacy on-chain does not automatically guarantee end-to-end privacy. Standard wallets query light servers to sync with the blockchain, and those network requests routinely expose identifying metadata including wallet addresses, transaction histories, birthday heights, and sync states. The blockchain itself stays shielded, but the light server learns your identity.
ZecPy is built from the ground up to prevent metadata leaks.
To verify this, we built a telemetry proxy that monitors and logs every outbound request during routine wallet tasks.
In side-by-side testing across five standard steps, two established Zcash wallets made 7 and 71 identifying requests respectively. ZecPy made zero.
In a full e-commerce simulation over Tor on testnet, ZecPy generated 108 requests with no identifying leaks, outside of one optional memo fetch that masked the transaction inside a batch of decoy payments. Our benchmark testing also uncovered three upstream bugs in core Zcash repositories, which we filed with fixes (librustzcash #3198, #3199; zcash-devtool #267).
This is fully functional software backed by multiple unit tests on a local devnet, real proofs, real blocks, and published testnet transactions. It is currently an alpha release and has not yet undergone a third-party security audit.
- Try the live request telemetry demo: zecpy-live.pages.dev
- Read the documentation and AI-agent specs: zecpy.pages.dev
put a lot of work into this
excited for what is to come
kindly check it out guys 🫶
Software is how money moves today, from SaaS subscriptions and API micro-billing to automated payroll and autonomous AI agents buying compute on demand.
Every standard payment leaves a metadata footprint detailing who paid, how much, and how often.
Python handles a massive portion of this financial infrastructure, but developers have never had a simple, native way to process private payments.
ZecPy solves this.
By running pip install zecpy, any Python backend, script, or AI agent can send and receive shielded Zcash in just a few lines of code.
It handles key tasks out of the box: issuing unique private addresses for every invoice, managing bulk payouts to dozens of recipients in a single transaction, supporting cold-storage offline signing, and setting hard budget caps for autonomous agents. Under the hood, it relies directly on Zcash's official Rust cryptography (librustzcash).
Privacy on-chain does not automatically guarantee end-to-end privacy. Standard wallets query light servers to sync with the blockchain, and those network requests routinely expose identifying metadata including wallet addresses, transaction histories, birthday heights, and sync states. The blockchain itself stays shielded, but the light server learns your identity.
ZecPy is built from the ground up to prevent metadata leaks.
To verify this, we built a telemetry proxy that monitors and logs every outbound request during routine wallet tasks.
In side-by-side testing across five standard steps, two established Zcash wallets made 7 and 71 identifying requests respectively. ZecPy made zero.
In a full e-commerce simulation over Tor on testnet, ZecPy generated 108 requests with no identifying leaks, outside of one optional memo fetch that masked the transaction inside a batch of decoy payments. Our benchmark testing also uncovered three upstream bugs in core Zcash repositories, which we filed with fixes (librustzcash #3198, #3199; zcash-devtool #267).
This is fully functional software backed by multiple unit tests on a local devnet, real proofs, real blocks, and published testnet transactions. It is currently an alpha release and has not yet undergone a third-party security audit.
- Try the live request telemetry demo: zecpy-live.pages.dev
- Read the documentation and AI-agent specs: zecpy.pages.dev
rex retweeted
Software is how money moves today, from SaaS subscriptions and API micro-billing to automated payroll and autonomous AI agents buying compute on demand.
Every standard payment leaves a metadata footprint detailing who paid, how much, and how often.
Python handles a massive portion of this financial infrastructure, but developers have never had a simple, native way to process private payments.
ZecPy solves this.
By running pip install zecpy, any Python backend, script, or AI agent can send and receive shielded Zcash in just a few lines of code.
It handles key tasks out of the box: issuing unique private addresses for every invoice, managing bulk payouts to dozens of recipients in a single transaction, supporting cold-storage offline signing, and setting hard budget caps for autonomous agents. Under the hood, it relies directly on Zcash's official Rust cryptography (librustzcash).
Privacy on-chain does not automatically guarantee end-to-end privacy. Standard wallets query light servers to sync with the blockchain, and those network requests routinely expose identifying metadata including wallet addresses, transaction histories, birthday heights, and sync states. The blockchain itself stays shielded, but the light server learns your identity.
ZecPy is built from the ground up to prevent metadata leaks.
To verify this, we built a telemetry proxy that monitors and logs every outbound request during routine wallet tasks.
In side-by-side testing across five standard steps, two established Zcash wallets made 7 and 71 identifying requests respectively. ZecPy made zero.
In a full e-commerce simulation over Tor on testnet, ZecPy generated 108 requests with no identifying leaks, outside of one optional memo fetch that masked the transaction inside a batch of decoy payments. Our benchmark testing also uncovered three upstream bugs in core Zcash repositories, which we filed with fixes (librustzcash #3198, #3199; zcash-devtool #267).
This is fully functional software backed by multiple unit tests on a local devnet, real proofs, real blocks, and published testnet transactions. It is currently an alpha release and has not yet undergone a third-party security audit.
- Try the live request telemetry demo: zecpy-live.pages.dev
- Read the documentation and AI-agent specs: zecpy.pages.dev
rex retweeted
SAY LESS BOSS, WE GOT YOU
GAMDOM TRUCK (G-TRUCK) ft GAMDOM FORCE (G-FORCE) ELITE for the #Gamdom100kRound2
Full content drops tomorrow! Follow and turn on your notifications. We moved the Z needle for @gamdom
rex retweeted
Zcash can keep a payment private. The application handling that payment can still expose someone’s wallet address, balance, or transaction history.
Imagine a developer building an invoice application with Zcash. They connect a wallet, display the available balance, add analytics to understand how people use the app, and include a support form for customers who need help.
Everything appears to work. Somewhere along the way, however, the analytics event includes a wallet address. A debugging statement prints the user’s balance. The support form collects their transaction history.
Those are ordinary application features carrying information they should have left alone. The blockchain can protect the payment while the application shares private wallet data somewhere else.
ZTrace helps developers follow that information through their code and find where it gets exposed.
A developer runs ZTrace against a JavaScript or TypeScript project. It looks for supported sources of sensitive wallet information, follows the data through the application, and identifies paths into logs, analytics, or network requests.
For each finding, it shows where the information came from, how it travelled, and the line that shares it. It also provides guidance on what to change.
That matters because the code reading a wallet address and the code sending it to an analytics service can live in completely different files. A developer reviewing either file on its own could miss the connection.
Under the hood, ZTrace uses TypeScript’s compiler tools to understand the structure of the code. Its analysis follows supported data flows through assignments, objects, function calls, and local modules. Developers can extend its coverage with adapters for their own libraries and configure policies for disclosures their application actually needs.
The source scan runs locally, keeping application code on the developer’s machine.
In the attached demonstration, I use ZTrace as the developer of Z Voice, an invoice application connected to a real Noir testnet wallet.
I install the packaged tool into that application and run a scan. It identifies three privacy problems: the wallet address reaching analytics, the balance reaching a console log, and transaction history being collected for support.
I then apply prepared changes to those parts of the application and scan again. The three findings disappear. The invoice acknowledgement and support features continue working with the unnecessary private data removed.
The report also keeps its manual-review notices visible, giving the developer a clear view of the code that still needs attention.
That workflow is especially useful as AI-assisted development becomes more common. We can produce working features quickly, but we still need to understand how those features handle people’s information. ZTrace gives developers a repeatable privacy check they can use while building, reviewing changes, and preparing a release.
The project also goes beyond reading source code.
Its browser-testing tools exercise an application with recognizable synthetic values and watch for those values appearing in supported console messages, HTTP requests, and WebSocket traffic. This gives developers evidence about what happened along the paths they actually tested.
Its Zcash-specific inspectors examine supported Unified Viewing Keys and PCZT files—partially created transactions that can contain sensitive information. These checks help developers review what an artifact reveals before sharing it with another system or person.
ZTrace is available through a command-line interface and reusable APIs. It produces readable terminal findings alongside JSON and SARIF reports for development tools and automated workflows. The repository includes an 88-case synthetic scanner benchmark, adversarial checks, browser integration tests, protocol test vectors, and documentation explaining setup, coverage, and troubleshooting.
I built ZTrace for Zecathon’s Core & Tooling track because developers building on @Zcash need practical ways to protect privacy throughout their applications.
The workflow is straightforward: follow the private data, find where it is shared, make the change, and check the result.
learn more: ztrace-x.vercel.app
github.com/ELLA0VICTOR/ztrac…
rex retweeted
🇰🇷 Muslims try to build a mosque in South Korea. The Koreans hold a pork BBQ in front of it 😂
rex retweeted
Strike's largest user vault holds $42,000 from 24 depositors. Its share price is 0.67. Everyone who joined at launch is down 33%.
following how a vault works on strike, you deposit, and a trader, the leader, trades the pool for you. You're buying their judgement. But you're also handing them total control. They can move your money into markets you never signed up for, take leverage you'd never accept, and keep trading straight through a drawdown. That vault holds 18 positions right now, 13 of them on a 20x setting. And the leader takes 25% of the upside while you carry all of the downside.
None of that means a leader is doing anything wrong. It means you have no way to hold them to your limits.
Your only real defence is to leave, and on Strike, leaving is slow. A withdrawal pays out a day after you request it, at whatever the vault is worth by then. So the damage isn't the moment the leader crosses your line. It's every hour after it, until you notice. If they break your rules at 3 a.m. and you file at 9, you've given them six more hours with your money, and your exit price pays for it.
Alerts don't fix this. An alert just tells you to start the clock yourself, after the fact.
So I built Rescind for the @strikeperps hackathon.
You set a mandate, four rules you'd hold any leader to: max effective leverage, allowed markets, max drawdown, and minimum leader stake. Rescind reads the vault every 5 seconds. The moment a rule breaks, confirmed on a second read so one bad read can't set it off, it files your withdrawal through the Strike API. Your exit clock starts about 10 seconds after the breach, not hours later.
And if the leader fixes it before payout, Rescind cancels the withdrawal. On Strike, that cancel is free. So filing on every breach and cancelling on every cure costs you nothing and always beats waiting. Strike's withdrawal design is effectively a free option, and Rescind is what exercises it for you.
It measures what a vault actually carries, not the label. Those 13 positions on a 20x setting add up to under 2x real exposure, and your rule fires on the real number.
Every action leaves a receipt that anyone can check against two public Strike URLs: the fill that broke your rule, and the withdrawal that answered it. No login, no trusting me.
Where it stands: detection runs live on mainnet against real vaults. My key is verified on Strike, and Strike accepts it on both the withdraw and cancel routes. The full breach → file → cure → free cancel cycle runs end to end against a simulated Strike. A live mainnet round trip just needs a funded account.
Self-hosted. Your key never leaves your machine, and Strike API keys can't withdraw to outside wallets.
Works on Mainnet.
Url: rescind-pi.vercel.app/
@sz8ng , @CardanoRami .