So we thought we should be transparent on why Sakura isn't on Ios yet
Apple has terms that doesn't allow paying for subscriptions in app with crypto
which is basically how sakura is built, the $sakura token is what's used to pay for so many things on the app and it goes against apple policy
We either have to change that or Send an appeal
Naturally no one can change how the sakura fee system works, cause I removed admin. this was to make it immutable so that the app just keeps sustaning itself as far as solana is alive Sakura will be alive
this is probably one of the flaws of an Immutable software and my goal now is to overcome this and get Sakura on Ios, if we do without any redesign. it's Proof that an Immutable software is the next stage of development and @toly was right
Please be patient with us. arigato
Introducing ZapPay! a crypto payroll for the modern business, built on starknet mainnet with the starkzap SDK.
Live app: https://t.co/GV1xKNfURb
GitHub: https://t.co/NK8iOcslF2
@starkience@Starknet@StarkWareLtd@adiiHQ
@W3Wag3s@starkience@Starknet@StarkWareLtd@adiiHQ Thanks, thatโs actually the next logical step Iโm taking in building zappay.
Next updates will have invoice status tracking to reconcile against payroll runs, and full on-chain transaction history pulling.
Still early but the foundation is there
Introducing ZapPay! a crypto payroll for the modern business, built on starknet mainnet with the starkzap SDK.
Live app: https://t.co/GV1xKNfURb
GitHub: https://t.co/NK8iOcslF2
@starkience@Starknet@StarkWareLtd@adiiHQ
Every transfer is signed by your wallet and settled on-chain in real time.
Live token prices fetched automatically so USD values are always accurate.
Built with Next.js 16, TypeScript, Tailwind CSS
How it was built:
Starkzap SDK network configuration to connect ZapPay to Starknet Mainnet via Cartridge RPC.
Starkzap token presets to resolve the correct mainnet contract addresses for ETH, STRK, USDC and USDT.