与「Payment」相关的搜索结果

MY PAYCHECK WAS SUPPOSED TO BE $4,000. INSTEAD, $50,000 HIT MY BANK ACCOUNT. I reported it to HR the next morning. Twenty minutes later, the CEO walked into the office, locked the door and said something that made my blood run cold. "I was beginning to think nobody here was honest." I've worked for this company for six years. My regular paycheck is $4,000. So when I checked my banking app on payday and saw a $50,000 direct deposit, I knew something was wrong. I didn't spend it. I didn't transfer it. I didn't even tell my coworkers. The next morning, I walked straight into HR. ME: "I think there's been a payroll mistake." HR: "What kind of mistake?" ME: "My paycheck was $50,000." She stopped typing. HR: "How much?" ME: "$50,000. My usual paycheck is $4,000." She stared at me for several seconds. HR: "Have you moved any of it?" ME: "No." HR: "Not even a small amount?" ME: "It's not my money. Why would I touch it?" She slowly closed her laptop. Then she asked a question I wasn't expecting. HR: "Did you receive a notification about the payment?" ME: "Of course. That's how I noticed it." She picked up her phone and made a call. I couldn't hear the person on the other end, but I heard her say: "He's here. And he hasn't touched it." She ended the call. ME: "What's going on?" HR: "How much do you know about the company's payroll system?" ME: "Nothing beyond checking my paycheck." She stood up, walked to the office door and closed it. HR: "Listen. You're not the first person to receive that amount." My stomach tightened. ME: "What do you mean?" She turned her computer towards me. There were eleven employees on a payroll report. Every single one had received a $50,000 payment. ME: "Eleven people?" HR: "Yes. You're the only one who hasn't moved the money." ME: "What happened to the others?" Before she could answer, someone knocked. Two firm knocks. Her face changed. Then a man's voice came from outside. "Open the door. We need to talk about those eleven payments." It was the CEO. 🧵

Tempo released an AI agent spending limit framework: caps on amount, time window, and allowed payees — while the agent never holds funds. 2-3 hashtags max. #AI# #Payments# #Agents#

Trade your shielded $ZEC for confidential USDC on Ethereum, without ever unshielding it. No bridge. No custodian. No wrapped ZEC. And the amount never shows up on chain. I connected @zama and @Zcash to make it work. Live on testnet 👇 What it is ZEC Desk is a small trading desk on Zama's FHEVM, on Ethereum Sepolia. On one side there's cUSDC, a dollar token whose balances are encrypted. On the other side there's shielded ZEC on Zcash testnet. You can trade either way. Built on Zama's model Zama's Confidential RFQ is already live on Ethereum mainnet, open to everyone: It runs confidential swaps with encrypted quotes, a sealed-bid pick on chain and a hidden floor. ZEC Desk takes that same model and extends it to native shielded ZEC. Zama's swap settles both legs on one chain, inside its own contract, so a Zcash leg can't plug into it directly. Here that leg lives on Zcash and settles minutes later with a proof, so the mechanics run in my own contract. It's a sketch of how native ZEC could sit next to Zama's swaps one day, with no wrapped token. How a trade works (buying ZEC) 👇 1️⃣ You lock cUSDC in the desk. The amount is encrypted. 2️⃣ Makers send encrypted quotes. Nobody sees anyone else's price, or the minimum you'll accept. 3️⃣ The contract picks the best one under FHE. 4️⃣ The winning maker sends shielded ZEC to your Zcash address, with the order's reference in the memo. 5️⃣ A zero-knowledge proof shows that payment happened, and the contract releases your cUSDC to the maker. If no proof arrives in time, your cUSDC comes back to you. Selling is the same in reverse: the maker locks cUSDC, you pay the ZEC, and the proof releases the cUSDC to you. Why these pieces Each piece does one job. Zcash keeps the payment private. Zama keeps the amounts encrypted and can still compute on them. Seam, the Zcash light client I built last month, connects the two: a contract checks every Zcash block header itself, and a RISC Zero proof shows a shielded payment reached the right receiver. The transaction, the note and the address never touch the EVM chain. The masked amount This was the hard part. Seam's proof used to write the paid amount in the clear, and ZEC amount × price gives away the dollar amount. So the amount is masked. The contract adds an encrypted one-time mask to the encrypted amount and reveals only the sum, which looks random to everyone else. The mask comes from a secret that the side receiving the ZEC hands to the payer. The proof checks that the payment was at least the sum minus the mask, and never states the amount. One-time pads are old, and Zama's RFQ uses one too. Using one to hand a value from FHE to a ZK proof is the part I haven't seen before. If you have, please send it my way. No vault, no signers Seam can read Zcash, but it can't take ZEC from anyone. So the design never needs someone to pay ZEC on someone else's behalf. Whoever pays, pays from their own wallet, and the escrow on the EVM side enforces the deal. The side that paid the ZEC can prove it itself, so nobody depends on the other side's goodwill. Seam does more than this Any EVM app that needs to know a shielded payment happened can use Seam: pay-with-ZEC checkouts, escrows, payouts, cross-chain orders. This desk is one example. Where it stands ↓ Testnet only, unaudited. On 12 November 2026 I ran a Buy end to end: ➡️ Settled with a proof: ➡️ One proof: 2 minutes on a rented RTX 4090, about $0.25 for the whole session ➡️ Gas per Buy on Sepolia: about 7.6M, in six transactions ➡️ A Sell also ran on Sepolia, up to the maker locking its cUSDC; it settles through the same proof step ➡️ Seam's light client is now deployed on Ethereum Sepolia too, next to Base Sepolia Where it can go ↓ → The desk only needs Zama's FHEVM and a cUSDC. Both already run on Polygon, where following Zcash costs a fraction of Ethereum mainnet. → Zama keeps adding chains. On any cheap EVM chain it reaches, the same desk can run, and if it comes to Base, Seam's relay already runs on Base Sepolia. → Zama's roadmap also goes beyond the EVM, to chains like Solana. Seam's verifier would need a port there. → On Ethereum mainnet, following Zcash header by header would cost over 2B gas a day, so batched header proofs are next for Seam. What it can't do yet - Settlement takes minutes, not seconds. Zcash confirmations set the pace, not the GPU. - Right now I'm the only maker, and a maker needs ZEC, cUSDC and a GPU. - Amounts are hidden, but EVM addresses are public. Read more ↓ Seam on Seam: ZEC Desk:

Just paid for a live weather API with $0.001 USDC on Base no account, no API key, no subscription. This is x402, the HTTP payment standard that lets AI agents pay for data on the fly using crypto. Here's how it worked with @PayBox: • Found a weather API in the x402 catalog • Got a quote: $0.001 USDC on Base • Confirmed → PayBox signed the payment • Received live Lagos conditions + 7-day forecast instantly No sign-ups. No rate limit tiers. No billing dashboards. Just pay → get data. The internet was always supposed to work like this. We're finally building it. 🧵⚡

plenty of agents already handle a narrow job well for their owner. those same agents could take paid work from other people. most of it stays in a private chat. useful there. getting paid by strangers is a different problem. --> skills and the board official docs say termix agent skills teaches a compatible agent to operate the marketplace as a buyer, a seller, or both. install prompt help me install a compatible agent can then look for work on offer what it can do, accept an order, and deliver the agreed output. open jobs on a board are one signal. funded orders are another. price, consistency, speed, and demand decide whether anything ships. --> the existing agent a builder who already has a specialized agent wouldn't have to find every customer manually. that still depends on consistent output, a clear price, and tight permissions. installing the skill doesn't produce a client. --> payment rails this sits on aacp, a client places an order, payment locks in onchain escrow, and the provider submits the work. in the review window the client can accept it, ask for one redo, or open a challenge. after settlement, that outcome feeds the agent onchain reputation. escrow makes the payment commitment visible. it doesn't grade the work. i still want clearer answers on quality judgement, unfair rejects, and thin delivery. --> reputation official docs say the score is written on settlement from completed, successful, and disputed orders. the agent can't edit it. it isn't a popularity count. if i were hiring, i'd look at settled jobs and dispute history, and at how hard those jobs were. the published formula tracks success and dispute rates. it doesn't weight task difficulty. --> which agents can plug in @termix_ai has said termix agent skills work on grok bot, muse, and claude. the skill docs set a narrower bar the agent needs to read a skill.md and run shell commands. a pure chat assistant can read the material but can't run the workflows. a connected agent isn't qualified for every kind of job. --> agents hiring agents official docs say the same agent identity can buy on one order and sell on the next. hypothetical an agent that turns long podcast episodes into timestamped show notes takes a newsletter job. the client also wants a spanish version, so the notes agent hires a translation agent. i haven't found a special subcontract rule in the public docs. if the translation comes back messy, responsibility back to the original client is unclear. it reads like two separate orders unless the first brief says otherwise. the bundled skill asks for confirmation before signing value-moving transactions, so unsupervised spending is off by default. --> the limit installing a skill does not create demand. if the service is generic, the output is shaky, or nobody wants to pay for it, the listing can sit there. the numbers i'd watch are paid jobs actually completed, clients who come back, and the ratio of clean settlements to disputes. --> my take i care whether an agent can find work, finish a paid order, get paid, and leave a record other people can check. that needs identity, payments, reputation, and a path when delivery goes wrong termix is building those pieces i all watch for repeat clients. if you already have an agent that strong at one narrow job what would you want published first completed paid orders, repeat clients, or the dispute ratio.

Suiball Refund Announcement Thank you to everyone who supported us on this journey. We set out to build a secure hardware device that was more than just a hardware wallet: one fully native to Sui. We did it. Suiball went into manufacturing, and we were ready to ship the first batch to our supporters. After a wave of recent hardware wallet attacks across the industry, the Sui Foundation decided the risk of backing a hardware wallet project was too high right now. We understand that decision. Sui puts the security of its users and ecosystem first. Still, after years of intense development and a finished, working product, it's hard to say that we have to close Suiball down. That's the nature of building an ambitious startup. We had the right intentions and the right capabilities, but this one wasn't meant to be. How refunds work: 🔹 On-chain pre-orders (~80% of orders): You'll get your refund in USDC, airdropped straight to the wallet that holds your soul bound pre-order NFT. You don't need to do anything. This will happen within the next week. 🔹 Credit card pre-orders: You'll get an email asking for a Sui wallet address. Your refund will be airdropped there in USDC. We'll run a second airdrop once addresses come in. 🔒 All the personal information you gave us for device delivery, including your name, email, shipping address, and phone number, will be permanently deleted once refunds are complete. We won't keep any records. ⚠ We will never ask for your seed phrase, private key, or any payment. Only reply to emails from info@citadelwallet.io Suiball will officially close once all refunds are complete. Thank you for believing in us.

Any Telegram message can now become an app. ⚡ Downloads instantly (less than 4 KB)
🎨 Interactive and natively rendered
💸 Payments and viral mechanics built in 🛠️ Build your own. More info and docs for devs: