Quote from: abhiseshakana on February 09, 2024, 07:09:48 PM

Quote from: Husna QA on February 09, 2024, 05:24:05 PM

Nah, yang saya maksud adalah sampai pada UTXO dan TXID yang akan digunakan (semisal pada challenge). Karena proses sync akan berulang setiap kali kita menjalankan kembali Bitcoin Core, atau dengan kata lain status full sync adalah ketika Bitcoin Core dalam keadaan running dan mencapai block terupdate.

Kalo untuk pengguna OS Windows lebih baik nunggu Blockchain full sync dulu aja, soalnya (yang pernah saya rasakan sendiri) pada saat proses IBD masih berjalan, program Bitcoin Core menjadi sangat tidak responsif (status sering not responding). Kalau dirasa-rasa malah bikin jengkel. Entah kalo buat OS lain (Mac atau linux) apakah juga merasakan hal yang sama?

Penasaran, barusan saya coba alihkan sementara folder data testnet3 agar sync dari awal kemudian create wallet dan coba menggunakan console (listunspent, dan lainnya) sementara proses sync masih berjalan di latar belakang, Bitcoin Core masih berjalan normal mas di MacOS entah untuk di Linux OS.

Quote from: abhiseshakana on February 09, 2024, 07:09:48 PM

Quote

Gunakan opsi Prune dan sesuaikan dengan kapasitas penyimpanan PC, dan ini juga bisa lebih menghemat waktu dan kuota internet agan jika memang dirasa berat jika full download data bitcoin blockchain

.
Menghemat storage mungkin iya, namun kalo menghemat waktu dan kuota internet kok rasanya tidak, soalnya pruned node juga akan tetap mendowload keseluruhan data Blockchain untuk proses validasi dan membangun database node, meskipun pada akhirnya data yang disimpan hanya sebatas size prune block storage yang dipilih.

Oalah, terima kasih atas koreksinya mas Zaki.
Barusan saya coba baca lagi mengenai prune ini, yang di rilis pada Bitcoin Core 0.11.0 (https://bitcoincore.org/en/releases/0.11.0/) ternyata perlu full validasi terlebih dulu sekalipun menggunakan Prune.

Quote from: https://bitcoincore.org/en/releases/0.11.0/

Block file pruning

This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. To recap, there are four types of data related to the blockchain in the bitcoin system: the raw blocks as received over the network (blk???.dat), the undo data (rev???.dat), the block index and the UTXO set (both LevelDB databases). The databases are built from the raw data.

Block pruning allows Bitcoin Core to delete the raw block and undo data once it’s been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or for rescanning the wallet. The block index continues to hold the metadata about all blocks in the blockchain.

The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the block index and UTXO databases. The minimum was chosen so that Bitcoin Core will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 blocks on disk.

Block pruning works during initial sync in the same way as during steady state, by deleting block files “as you go” whenever disk space is allocated. Thus, if the user specifies 550MB, once that level is reached the program will begin deleting the oldest block and undo files, while continuing to download the blockchain.

For now, block pruning disables block relay. In the future, nodes with block pruning will at a minimum relay “new” blocks, meaning blocks that extend their active chain.