Posts

Tangem Wallet Pack of 2 - Secure Crypto Wallet - Trusted Cold Storage for Bitcoin, Ethereum, NFT's &

Tangem Wallet Pack of 2 - Secure Crypto Wallet - Trusted Cold Storage for Bitcoin, Ethereum, NFT's &
Key item features Ultimate Security: Generates a private key that remains on the card, safeguarding crypto and NFTs from hackers with EAL6+ certification and audited firmware. Versatile Compatibility: Manages over 13,000 tokens across 70+ blockchains, supporting DeFi, NFTs, and DeEx without wires, Bluetooth, or USB. Effortless Operation: Utilizes NFC for secure transactions via a mobile device and the Tangem app, enabling buying and selling crypto with various payment methods. Smart Backup: Features a second Tangem Wallet as a backup, eliminating the need for paper, pictures, or seed phrases for recovery. Durable Design: Boasts IP68 protection against environmental conditions, ensuring longevity and robust physical security. Comprehensive Support: Compatible with Bitcoin, Ethereum, Solana, XRP, USDT, and over 6,000 cryptocurrencies, integrating with dApps and WalletConnect.

Why use Elligator Swift Encoding - BIP 324?

What is the reason behind using Elligator Swift encoding in BIP-324 ? I gather that it is used to prevent fingerprinting. Is there any other reason ? Thanks from Recent Questions - Bitcoin Stack Exchange https://ift.tt/Wv0tsTx via IFTTT

LBANK

Why does BIP-110 require a 55% signaling threshold if its nodes reject non-signaling blocks?

During the signaling period, BIP-110 nodes reject blocks that do not signal support. What, then, is the purpose of the 55% activation threshold? From the perspective of a BIP-110 node, would the threshold not always appear to be met, since every block it accepts during that period must already be signaling? Or is the 55% calculated using blocks from the full proof-of-work chain, including blocks that BIP-110 nodes consider invalid? from Recent Questions - Bitcoin Stack Exchange https://ift.tt/382CIDW via IFTTT

Signet Funding Request - Developer Wallet Refill

I am currently configuring and testing a local development environment on the Bitcoin Signet network. My node and local indexing infrastructure are fully synchronized, but I have run into roadblocks utilizing the public web faucets to acquire test tokens.Could an active node operator or community member please send a small amount of testnet coins (sBTC) to my Taproot address? Any amount to cover local transaction fee testing would be greatly appreciated. If there are other ways to get testnet coins please let me know. Signet Receive Address:tb1pcv9ft8du42wwkr0yvu2vssj0ugsjg7tw7p6c4e28rt45cnzrgvesq7rtea Thank you for your time and assistance. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/eF8pWGI via IFTTT

TRADE GPT IA demande d'avis utilisateurs

Bonjour à tous, est-ce que quelqu’un ici connaît Trade GPT ? J’ai vu plusieurs sites et je ne sais pas lequel est le bon. Est-ce que le site officiel est bien https://www.tradegpt-ia.com/ ? Si certains l’ont déjà utilisé, je serais intéressé par vos avis. Merci d’avance ! from Recent Questions - Bitcoin Stack Exchange https://ift.tt/twKvbn1 via IFTTT

Why no widespread support for payment references/additionnal TX Data?

This might sound like a dumb question, but bear with me — it's a real one With traditional bank transfers in a business context, it's standard practice to attach a reference to the transaction (invoice number, customer ID, etc.) so that both parties can reconcile it against their accounting ledgers. I know the recommended practice with Bitcoin is to generate a fresh address per transaction/invoice, which gives you both better privacy (and arguably quantum resistance) and unambiguous reconciliation. Still, that only works when you control the receiving side. The Bitcoin network supports embedding additional data in transactions (OP_RETURN), and EVM chains have the calldata/input data field. So why is it so uncommon for applications — not just browser wallets — to let the sender attach a reference when sending funds? If blockchain payments are ever going to reach mainstream business adoption, this seems as obviously useful as a bank payment reference. I'm ask...

Reliable source

Look, engaging with the authorities is a marathon, not a sprint. By methodically filing these reports, you’re not just fighting for your own funds—you’re contributing to the broader battle against crypto crime. For a deeper dive into what to do after a theft, check out (Reclaimeasy At Gmail C0m) for complete guide on how to recover stolen crypto from Recent Questions - Bitcoin Stack Exchange https://ift.tt/fMJ27Xm via IFTTT

Difference between long-term-fee-rate and discard fee-rate

In the bitcoin-core codebase, it seems that discard fee-rate and long-term fee-rate are used interchangeably when computing the cost of change. Consider the following code excerpts: cost_of_change = discard_feerate.GetFee(change_spend_size) + effective_feerate.GetFee(change_output_size); ref: https://github.com/bitcoin/bitcoin/blob/2990bd773551c835ab0b6b59d85730adab2fd428/src/wallet/spend.cpp#L1182 and also: cost_of_change = effective_feerate.GetFee(change_output_size) + long_term_feerate.GetFee(change_spend_size); ref: https://github.com/bitcoin/bitcoin/blob/2990bd773551c835ab0b6b59d85730adab2fd428/src/wallet/test/fuzz/coinselection.cpp#L96 In both of these snippets, the cost_of_change is being computed, however, one uses the long-term fee-rate while the other uses the discard fee-rate. Are these two terms actually distinct or can they be used interchangeably? To my knowledge, cost_of_change should be calculated using the discard fee_rate, and the long_term fee_r...