There are few ways :
1. If you're running full node, add address as watch-only address. Then configure walletnotify to run script (https://bitcoin.stackexchange.com/questions/24457/how-do-i-use-walletnotify)
2. Use 3rd party API/service which notify when there's transaction related with specified address

Stop promoting your centralized & closed-source wallet service. Your wallet service is the opposite of what Bitcoin trying to reach, which is decentralization and full control over your money.

Wallet such as Electrum might be harder to use, but it's better than lose pseudonymity & full control over your coins.There's no difference between bank and your service, expect different currency choice.


Usually you don't need to as almost all spam/off-topic are deleted in this section, even if it's made by reputable member.
Most of the times, spam are done by newbie / newly created account and all of them are deleted.

While i agree with your opinion, most of the hurdle comes from :
1. Wallet developer who don't bother upgrade their wallet to support newer Bitcoin features (Bech32 SegWit, Payment protocol, RBF, etc.)
2. No automatic update or message to upgrade wallet to latest version
3. User choose bad/centralized wallet (freewallet, coinbase, etc.)
4. There's no implementation guide/standard yet, such as signing message with Bech32 address (no idea if there's standard now)

The only way to unify bitcoin's transaction standard (without hard-fork which force user and developer update their wallet) that i could think are :
1. Constantly ask wallet's company/developer to support newer features
2. Encourage user only to use wallet which support newer features (and decentralized obviously)
3. Boycott all wallet/services which don't support newer features (Last resort)

It's quite confusing (since there are various changes), but AFAIK :
1. Mastercoin is rebranded as OMNI. You can check basic info at https://www.openmarketcap.com/tokens/omni or https://coinmarketcap.com/currencies/omni/
2. OMNI is part of OmniLayer platform. The most popular usage was Tether/USDT and there's list of OmniLayer usage at https://www.omniexplorer.info/properties/production.
3. Most tasks are done on OMNI network, not on Bitcoin network. With 4-Layer internet model as analogy, Bitcoin is Network Layer while OMNI is Application Layer.


Just post it on serious discussion, you won't get accurate/detailed answer on Altcoin discussion. Even if you self-moderate the thread, your thread will be buried quickly.

1. MimbleWimble is actively developed, but not for Bitcoin. It lacks support from Bitcoin community, mainly because it's not popular and not compatible with bitcoin script
2. TumbleBit already available today on Breeze Wallet
3. Schnorr Signatures is actively developed, but it took long time since there's no standard for it
4. Confidential Transactions won't coming to Bitcoin since it has scalability trade-off (bigger transaction size and longer verification time). Most privacy-based cryptocurrency use it though

Also, there are few upcoming proposal which are interesting

• Dandelion
• MAST
• Eltoo
• Bulletproof (useless unless CT is used as well)

Edit : looks like Pmalek already answer your question while i verify my memory

1. Settings > Options


2. Enable "Prune block storage" then input storage size



Easiest guide that i could find https://bitzuma.com/posts/moving-the-bitcoin-core-data-directory/

P.S. External HDD isn't best storage option since there's higher chance block/wallet corrupted.

Pruning only reduce storage space used by only store x latest blocks, you still need to download (and verify) all blocks. That's why it took so long.


Only running full nodes is easy, but configure it for specific usage (such as payment services) is tricky.


Because you chose the hard way, there are some better alternatives which don't involve 3rd party such as :

• https://github.com/btcpayserver/btcpayserver
• https://github.com/cryptoapi/Payment-Gateway
• http://docs.electrum.org/en/latest/merchant.html

FYI, some people refer native SegWit address (starting with bc1) as Bech32 address and refer nested SegWit address as P2SH SegWit address. Just in case so you won't be confused with the terminology.

While SegWit have many advantage which mentioned by BitCryptex, not all Bitcoin wallet support sending Bitcoin to Bech32 address (but all of them support send to nested SegWit address).

Yes. It's called chainstate, few call it UTXO set.


AFAIK it's true, chainstate uses key/value pair method which contain TX hash and block hash.


By access chainstate, not access blocks

---

You meant pseudonymous

You mean use HDD to mine Proof-of-Capacity such as burst coin? If so, then the answer is no. Mining calculator such as https://blocks.fastpool.info/calculator & http://burstcoincalculator.com/ show that you only get about $1-$2/month, without calculating electricity cost.

I don't know much about decentralized cloud storage, but https://storj.io/ homepage mention you will get $0.015/GB/month which mean you could earn up to $120/month.

Technically, it's on-chain flaw where miners can choose specific transaction to be included/excluded.


Where's the source? There's no such information on twitter or reddit. Even if it's true, i doubt they would do that for long since it's MAD scenario since they could lose value of mined Bitcoin since people might be panic (unless they don't care about wasting money or losing profit).

But AFAIK when there's 2 valid conflicting transaction which have different height timelock, the transaction with lower height timelock included on-block.

Solusi-1 saya setuju, tetapi itu solusi termudah supaya fee tidak terasa berat bagi pelanggan
Solusi-2 solusinya adalah langsung menjual/konversi cryptocurrency ke fiat. Bisa dilakukan secara manual maupun menggunakan payment processor seperti BitPay yang langsung konversi cryptocurrency ke fiat dengan fee tertentu.
Solusi-3 bukan putus, tetapi membuka attack vector untuk mencuri koin yang seharusnya tidak dipunya seperti yang dijelaskan di https://bitcoin.stackexchange.com/questions/55310/do-parties-in-a-lightning-network-channel-need-to-be-online. LN (dan sejenisnya) lebih cocok sebagai solusi ketika arsitektur LN sudah bisa mencegah hal tersebut, online 24/7 sudah bisa dicapai oleh mayoritas orang atau penerima koin selalu online.


CPFP (Child-pay-for-parent) alias menggunakan UTXO/koin yang belum dikonfirmasi dalam transaksi bisa menjadi solusi karena :
1. Membuat transaksi yang dibuat oleh pelanggan lebih cepat dikonfirmasi
2. Pelanggan dan pemilik warung makan tidak perlu khawatir transaksi tidak akan terkonfirmasi

Tentunya transaksi dengan CPFP harus memiliki fee yang sama atau lebih tinggi dibandingkan fee yang dibuat oleh pelanggan supaya efektif.

Ada 3 solusi untuk hal ini :
1. Harus ada minimal total pembayaran supaya fee transaksi terasa kecil. Beberapa bitcoin cryptocurrency processor seperti BitPay memberikan minimal $5 untuk pembayaran dengan Bitcoin.
2. Menggunakan cryptocurrency dengan fee yang kecil, meskipun pada umumnya hanya berlaku pada cryptocurrency yang tidak terkenal atau semi-centralized.
3. Hanya menerima cryptocurrency melalui off-chain transaction seperti Lightning Network, meskipun fee akan tinggi jika tidak ada jalur/path antara penjual dan pembeli karena harus membuat 1 on-chain transaction untuk LN channel.


0 konfirmasi (atau bisa disebuf 0-conf) tidak teralu beresiko juga :
1. Penjual hanya menerima transaksi tersebut jika fee yang dipakai dalam transaksi tidak dibawah rata-rata. Seller bisa menggunakan API seperti dari website https://bitcoinfees.earn.com/ untuk mengetahui apakah fee yang dipakai dibawah rata-rata/tidak.
2. Mengecek apakah ada double-spend di bitcoin network. Hal ini bisa dilakukan dengan mengecek transaksi/alamat pengirim di beberapa block explorer atau cek mempool di node.


Saya setuju dengan saran ini

Anyone who suggest KYC in cryptocurrency space shouldn't use cryptocurrency in first place and keep using fiat (exception for centralized exchange and few merchant). I would rather leave this forum rather than give my identity.
Even CloudFlare implementation is enough to make good member who want preseve their anonymity left this forum.

If we want to prevent spam, scam or merit farming, disable signature and remove bounty child board are better option.

TLDR : Your idea can go to hell.

After i upgrade to most recent version, i keep receive message "WARN    global  src/p2p/net_node.inl:1338       No incoming connections - check firewalls/routers allow port 18080". Should i leave it alone or configure my firewall or/and router?


It took some time since it actually upgrade database version, not sync process. In my case, restart both CLI and monerod fix the problem.

Sorry, but based on my understanding, your explanation don't clear any of my doubt/question. In fact, now i have more doubt/question.


Then you shouldn't said "...grouped together into a block", it makes people confused.


This is ridiculous since one-time address has become standard to improve privacy. Most HD wallet also generate lots of addresses in advance.


High computational power required to generate an address won't stop the problem. There are few critical questions such as :
1. What stopping attacker from double-spend attempt (example : attacker make 2 transactions (from an address contain 1 coin) where 1st transaction is sent 1 coin to Bob & 2nd transaction is sent 1 coin to Alice)?
2. How do new nodes verify the balance is valid and not comes from thin air? Even ETH which uses Balance model (not UTXO like Bitcoin) still require storing transaction.


You meant transaction would have faster confirmation time if the number of transactions increases. It's not really scalable since time required to verify the transaction and bandwitch to broadcast the transaction/list are growing linearly (O(n))

Yes, my ideology is never buy token (if their project don't need token/ICO or no strong proof they have working product/server which is better than competitor in most aspect).

Monero categorized as cryptocurrency/coins, not Token. Besides, privacy isn't a crime.

Basically get all transaction hash in a block and do the merkle tree operation.

Full nodes only send necessary/part of merkle tree to verify the transaction.

This image/ilustration might help you : https://cdn-images-1.medium.com/max/1600/0*lR_IMzUjQUJgXq5A.png


AFAIK full nodes client store such information to prevent re-computation, but each full nodes client use have different method/implementation.

Selain point-point yang disebutkan oleh mu_enrico, alasannya adalah :
1. Tidak mengetahui bahwa plagiarisme adalah sebuah kejahatan dan melanggar UU No 28 Tahun 2014 tentang Hak Cipta dan beberapa peraturan lainnya.
2. Tidak pernah merasakan ketika hasil kerja mereka diklaim orang lain.