Lightspark has released a prototype called dotMoney, according to a post by Bitcoin News on X, introducing a way to send test funds through shared links, .money files, or directly between nearby iPhones. The setup allows .money files to be transferred over AirDrop, sent through messaging apps, or stored on a USB drive, while the underlying funds move between wallets through Spark. The company said each file can be redeemed only once, meaning copied or forwarded files do not create duplicate funds. Senders can also cancel payments that have not yet been claimed. For now, the prototype runs on test funds with no monetary value. Lightspark is also using Grid to test withdrawals to banks, Cash App, and the Lightning Network. The update outlines how the company is experimenting with file-based and link-based payment delivery while keeping settlement at the wallet layer.
Lightspark has released a dotMoney prototype that lets users send test funds through shared links, .money files, or directly between nearby iPhones, according to a post from Bitcoin News on X.
The post said .money files can be sent through AirDrop and messaging apps, or stored on a USB drive. The underlying funds move between wallets through Spark.
Each file can be claimed only once. Copying or forwarding a file does not create duplicate funds, and the sender can cancel a payment if it has not been claimed.
For now, the prototype uses test funds with no monetary value. Lightspark is also testing bank withdrawals, Cash App withdrawals, and Lightning withdrawals through Grid.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
