**#CakeWallet the only mature wallet out there that I know of that is doing anything rn to further the privacy of Bitcoin transactions with full send, receive, and privacy preserving scanning support for Silent Payments**
**Silent Payments**
Silent Payments (BIP-352) is a protocol for static payment addresses in Bitcoin without on-chain linkability of payments or a need for on-chain notifications.
This protocol protects the receivers privacy by automatically having the sender generate a new Taproot address on chain only the receiver can know is theirs and spend from everytime a transaction is sent to their Silent Payments address.
For a more detailed explanation on how Silent Payments works, please visit https://silentpayments.xyz/
One major difference of Silent Payments is in order to fully protect the privacy of the user and not have the server know which Silent Payments transactions belong to them, we opt for on-device scanning of transactions instead of having a light wallet and making the node do all the work for us. This incurrs greater synchronization time, device power consumption and hardware utilization, but protects the privacy of the user much more.
Silent Payment addresses start with ```sp1```
**Scanning**
In order to enable Silent Payments, tap the switch on the “Silent Payments” card to start scanning blocks for Silent Payments.
The wallet will start scanning from the height of when you first opened it after installing 4.18.0 or higher, or continue where it left off. Silent Payments scanning will automnatically turn off once it has reached the current blockheight. If you would like it to automatically scan for Silent Payment transactions on new blocks, please toggle an option under Menu -> Silent Payments settings -> “Set Silent Payments always scanning” to on. Silent Payments scanning will automatically toggle on if there are new blocks to scan and toggle back off when it’s finished.
**Receiving**
In order to receive a Silent Payment, you must give the sender your Silent Payments address, which can be found by switching the address type to Silent Payments following the instructions at the beginning of this page. When you want to receive the transaction in the wallet, you must enable Silent Payments scanning.
**Sending**
You can send Bitcoin to an existing Silent Payments address (```sp1xxx```) using the same flow. No extra work is required to send to a Silent Payments address, the wallet will handle the unique address generation in the background before sending your transaction.
Learn more here:
https://guides.cakewallet.com/docs/cryptos/bitcoin/#silent-payments
Hope they are able to stay operating and not be agora desked or local moneroed...
Where my #monero people at?
https://video.nostr.build/04655dc6e49428144cf6d662c3a8395eb29284c3e0492a21c124e5404377bb85.mp4
Today I am here, tomorrow I do not know.
The important question to be asked here is the following: but did you "have a good time with your bitcoin and your crypto and everything else that you're playing with"?
I've got a really neat collection of blades too. I wish I could share it but it would blow my opsec. Great find, congratulations!
Why are #benzos not working anymore?
People can accept your money but, since it is no KYC, miners won't include your transactions in a block, no matter the fee you pay, so you end up not transacting. Basically you are locked out of your money. That is the bright future I envision for BTC and it is a shame.
Yes, but can you afford the hookers?
You're describing almost everyone I know. It is sad but true.
#Ledger launches #LedgerFlex, a mid-range hardware #crypto wallet
https://techcrunch.com/2024/07/26/ledger-launches-ledger-flex-a-mid-range-hardware-crypto-wallet/
#privacy #cybersecurity
Does it include a complementary backdoor?
We are heading to fuckville and it won't be nice.
MARA reminds me of MS-13, Mara Salvatrucha 13. Maybe because they gangstas?
Been using Venice.ai lately, to test it out. They market themselves as protectors of users privacy because a proxy is used between the LLMs and the user. So here follows the interaction I've had with it, regarding my lack of trust that the proxy will be the cure for privacy matters:
"you claim to be a privacy service because you route all prompts through a proxy and not directly to the model. But, this way, isn't the proxy a privacy violator, since it knows the prompt and where the prompt came from?"
"The proxy in Venice.ai does not store or access any user prompt data, and it only acts as a mediator between the user's browser and the AI model. The proxy is designed to protect users' privacy by anonymizing their requests and ensuring that no personal information is leaked. While the proxy does receive the user's prompt, it cannot associate it with any specific user or session, so it remains an anonymous entity to the proxy itself . This approach provides a reasonable level of privacy protection while still enabling users to interact with AI models on Venice.ai.
Reference: Venice.ai Privacy Policy. (n.d.). Retrieved from <https://www.venice.ai/privacy-policy>"
"How can a user verify this? Does it have to trust you?"
"As a user, you don't have to fully trust Venice.ai's privacy claims. Instead, you can perform some basic checks and verify the proxy's behavior for yourself:
1. Check your browser settings: Ensure that no cookies or other tracking data is being stored by the proxy. If the proxy were storing this information, it would be possible to identify individual users.
2. Inspect the network traffic: Use a tool like Wireshark or Charles Proxy to monitor the network traffic between your browser and Venice.ai's proxy. You should not see any identifiable user data being transmitted.
3. Test for IP address leakage: Run an online test, such as ipleak.net, to check if your actual IP address is being exposed. If the proxy were leaking your IP address, this test would show your real IP information.
While these checks can provide some assurance, it's essential to note that no system is perfectly secure or private. Venice.ai has implemented various privacy measures to protect user data, but ultimately, users should always remain vigilant and take responsibility for their own online privacy.
Reference: Venice.ai Privacy Policy. (n.d.). Retrieved from <https://www.venice.ai/privacy-policy>"
"So why not open your code?"
"Venice.ai is a commercial product that uses proprietary AI models and technology to provide its services. While they do not open-source their code, they have implemented several measures to ensure user privacy and security:
1. End-to-end encryption: Venice.ai's communication with users is encrypted using industry-standard methods, such as TLS/SSL.
2. Anonymous requests: As mentioned earlier, the proxy receives anonymous requests from users, making it difficult for anyone to associate a specific prompt with a particular user.
3. Data retention policies: Venice.ai does not store any user data on their servers, ensuring that no personal information is available even if their systems were compromised.
While open-sourcing the code might provide additional transparency and trust, doing so could also compromise their competitive advantage in the AI market. Furthermore, proprietary software often has better performance and security compared to open-source alternatives, as it can be optimized for specific use cases without being constrained by open-source licenses or requirements.
Reference: Venice.ai Privacy Policy. (n.d.). Retrieved from <https://www.venice.ai/privacy-policy>"
To be honest, I am not buying the privacy angle.
What is your opinion? Great tool, otherwise.
#aksnostr #veniceai #venice.ai #ai #privacy #agi #infosec #opsec #cybersec #artificialintelligence #chatgpt #gpt #llm #llama #largelanguagemodel #model #agi
Yes, I pay everything normie in cash. Fuck surveillance!
Fuck! He outbid me for 1000 sats!!!