This is clearly XY problem, if your goal requires master private key, private key, public key or bitcoin address, then as @achow101 mentioned, just open it in Bitcoin Core.
It's different story if the wallet.dat is encrypted and you don't know the password.
|
|
|
There's too many bias when we're talking about altcoin. For example, some consider ETH is shitcoin which allow various shit tokens exist, but few people like ETH due to it's smart contract and allow few things such as gambling, DEX and games. If altcoin giveaway were to be allowed, IMO there are few restriction or treatment must be made to prevent total chaos such as : 1. Signature is completely disabled 2. Only Jr. Member or above allowed to post 3. Shows warning, just like thread on "Investor-based games" board. Modified example from "Investor-based games" board : Warning: You are in the Altcoin giveaway section. It's likely you will lose your money, become victim of identity theft and/or receive malicious message on your email/social media. Additionally, moderators do not remove likely scams. You must use your own brain: caveat emptor. Do not gamble more than you can afford to lose.
|
|
|
I think the testnet blockchain is similar to the size of the litecoin blockchain and on my dual core 2GHz laptop, it seemed to take only about 8 hours to download and store the entire thing. It's not the best but if you really need it it's not that bad - load it up before sleep and wake up with the full sync.
That is 22.5 GB blockchain, ignoring the chainstate. It's a bit high just to broadcast one block, not to mention eventually I am going to download it with my own code as soon as I can fix my P2PNetwork namespace which is why I don't want to do it twice. That's certainly wasteful of resource (especially if you have slow connection), i assume software you use can't connect to Bitcoin Core client? P.S. i have fully synced testnet full node (originally used to learn more about Bitcoin, but eventually only used to test LN in past), PM me if you trust me to broadcast it.
|
|
|
I mean Coinbase wallet app there, not exchange wallet. So it is a completely hot wallet that you can use it when you are online. And I have no technical information about Atomic wallet. And I didn't comment on its safety. I just reminded that there was no problem yet with Atomic wallet.
If you mean this one ( https://play.google.com/store/apps/details?id=com.coinbase.android), then there's no difference since there's no option to obtain private key/seed and you're required to sign up.
|
|
|
I never try it, but Bitcoin Core console have command called submitblock which used to submit new block to network. Here's help information from Bitcoin Core. submitblock "hexdata" ( "dummy" )
Attempts to submit new block to network. See https://en.bitcoin.it/wiki/BIP_0022 for full specification.
Arguments: 1. hexdata (string, required) the hex-encoded block data to submit 2. dummy (string, optional, default=ignored) dummy value, for compatibility with BIP22. This value is ignored.
Examples: > bitcoin-cli submitblock "mydata" > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "submitblock", "params": ["mydata"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
|
|
|
Bukannya tidak ingin ikut berdiskusi, tapi memang tidak paham dengan apa yang didiskusikan, "gag nutut" bahasa kerennya gitu. Terkadang satu buah pertanyaan sudah cukup untuk memicu lahirnya diskusi Gan. Jadi meskipun si penanya tidak menguasai topik tersebut, tetapi dia sudah memiliki andil pada alur diskusi yang tercipta. Hanya jika pertanyaan tersebut bersifat konstruktif, sebagian pertanyaan umumnya 1. Sudah dijawab sebelumnya (baik di thread atau reply lainnya) 2. Tidak terlalu berhubungan dengan topik yang bahas (bisa menyebabkan off-topic)
|
|
|
Bit of humor. The RPi2 and RPi3 look very similar. When they are in a clear case they are almost impossible to tell apart.
You then can spend about an hour trying to get the non existent wi-fi on a RPi2 to work.
I may possibly have some recent experience with this.
Also, for sale 1 slightly used RPi2 only thrown at wall once.
-Dave
Tip : you can use command sudo dmidecode -t1 to find type of your raspberry, notebook or motherboard. neofetch also can show your device type & specification in general.
|
|
|
Many of those you mentioned do publish useful information, but in fact there is already a special topic where anyone can publish unmerited good posts - [self-moderated] Report unmerited good posts to Merit Source. Of course, we should first ask @LoyceV if he would be against publishing posts in other languages in his topic. Still, this is the main section and there are quite a few merit sources for speakers of different languages. Report self-made post or post with any language is allowed there, but don't expect too much since there aren't many source who're willing to use Google Translate (if they don't understand the language) or bother see self-made post
|
|
|
There's no single universal driver for all Linux distro, if you don't want bother to research about install/configure AMD driver for Linux distro you use, then how about use Linux distro which specifically created for mining such as http://ethosdistro.com/ or https://simplemining.net ?
|
|
|
Namun apakah tidak menghalangi miner untuk mengkonfirmasi transaksi jika node tersebut berbeda dari asal?
Tidak ada masalah. Miner tidak akan mempermasalahkan siapa yang ngirim transaksinya ketika membuat blok. Bisa dicek di https://en.bitcoin.it/wiki/Block. Dan, apa bisa dikatakan Dandelion ini mixer-nya untuk node?
Walau tujuannya sama-sama privasi tapi ane rasa cara kerjanya cukup berbeda jauh. Pihak 'ketiga' yang menjadi jembatan antar node tidak ada (seperti mixer yang punya pihak ketiga). Bagi ane, mungkin lebih mirip dengan Coinjoin-nya node. Bisa dicek juga perbedaan yang udah di post oleh agan ETFbitcoin. Tujuan CoinJoin dan Dandelion sangat berbeda, secara simpel : * Coinjoin : Menyembunyikan hubungan antara pengirim dan penerima Bitcoin (dengan cara menggabungkan beberapa transaksi) * Dandelion : Menyembunyikan IP (yang digunakan untuk mengirim transaksi Bitcoin ke jaringan Bitcoin)
|
|
|
If you only need to get all block header (not specific ), then all you need to do is follow @nc50lc suggestion. There are alternative besides using Bitcoin Core or https://chainquery.com, such as https://www.blockcypher.com/. But if you need to get header of specific block (which comes from SlushPool API), first you need to get list of block height returned by SlushPool, then use another API to obtain header of the block.
|
|
|
sehingga jika ada suatu sistem supernode yang mampu memetakan perutean transaksi tersebut, maka IP address dari node pembuat transaksi akan dapat dilacak oleh supernode tersebut.
Hal tersebut sangat susah karena : 1. 1 node umumnya hanya memiliki 8 outgoing connection 2. Tidak semua node membuka incoming connection (yang sangat diperlukan untuk pemetaan) 3. Beberapa node menggunakan IP dinamis (IP bisa berubah sewaktu-waktu)
|
|
|
1. Yang ane baca dari berita-berita, BIP156 masih belum diimplementasikan dan butuh waktu lebih lama lagi.[1] Apakah ini reliable?
Sejauh yang saya tau, tidak ada perkembangan mengenai implementasi Dandelion untuk Bitcoin karena DoS problem (sesuai dengan sumber [3] yang dicantumkan). Selain itu, Dandelion tidak menyelesaikan masalah fungibility. 2. Ane baca juga dari sini[2], walau beda implementasi, sepertinya node yang menjalankan dandelion bisa 'diintercept' atau mungkin seorang penyerang bisa ngesniff data dari node. Sepertinya ini berhubungan dengan poin 3 yang disebutin om ETF di atas. Apa ada perkembangan untuk mengatasi serangan semacam ini?
Yang saya tau, hanya ada 1 paper yang membahas masalah ini yaitu Dandelion++: Lightweight Cryptocurrency Networking with Formal Anonymity GuaranteesTetapi hampir tidak ada diskusi atau review apakah paper tersebut berhasil mengatasi masalah deanonymization secara efektif. 3. Apakah problem yang dijelaskan/didiskusikan di sini[3] sudah mendapatkan solusinya? Ane agak kesulitan mencari bacaan karena rata-rata berita yang muncul cuma mengulas seputar dandelion dan bagaimana protokol itu bisa membantu meningkatkan privasi bitcoin tapi ga ada follow-upnya. Selain itu, pull request juga diclose karena sepertinya belum ditemukan solusi atas serangan DOS (sejauh yang ane pahami).[4] Dan tidak ada lagi milestonenya setelah dihapus dari 0.18.[5]
Terakhir kali saya melihat Bitcoin-dev mailing dan komunitas yang hanya membahas sisi teknikal Bitcoin, belum ada solusinya.
|
|
|
Yes, i know the fork on BCH was to increase the block size, but i didn't know BCH avoid segwit. I used to think the bigger blocks was a nice solution to avoid the network getting stuck with unconfirmed transactions, but that solution in the long run only would bring a crazy heavy blockchain.
Thanks for the info guys.
Then you should research about Schnorr Signature and Taproot as well. P.S. if you're satisfied with the answer and don't have any question related to the main topic (block size), consider lock the tread. The witness data can occupy up to 60% percent of a block size but with Segwit this data is omitted from the main blocks.
Theorically it's almost 75%, even though it requires transaction where it's signature is very big (very rare). Besides, i wouldn't say the signature part is omitted from "main" block since it's only moved to witness space on block and signature is very important part of transaction/block. Transaction's signature or witness part only committed/removed if your client/wallet doesn't support SegWit.
|
|
|
Pinned thread on Bitcoin Discussion board is also outdated, thread for 0.19.1 already exist at https://bitcointalk.org/index.php?topic=5231808.0Yeah but if you click the link it takes you to the correct version. Just theymos have no time for it right now.
Not if you choose torrent link
|
|
|
2020-03-11T03:12:01Z ERROR: ProcessNewBlock: AcceptBlock FAILED (AcceptBlock: Failed to find position to write new block to disk (code 0)) 2020-03-11T03:12:06Z ERROR: SerializeFileDB: Rename-into-place failed 2020-03-11T03:12:06Z *** Flushing block file to disk failed. This is likely the result of an I/O error.
2020-03-09T20:42:16Z ERROR: DeserializeFileDB: Failed to open file D:\Bits\banlist.dat 2020-03-09T20:42:18Z Failed to open mempool file from disk. Continuing anyway. 2020-03-10T02:06:34Z ERROR: WriteBlockToDisk: OpenBlockFile failed 2020-03-10T03:54:22Z ERROR: ProcessNewBlock: AcceptBlock FAILED (AcceptBlock: Failed to find position to write new block to disk (code 0))
Based on above error message (i only take few relevant lines), either your HDD (most likely reason), your USB/SATA cable or your motherboard (specifically USB/SATA controller) are the the fault. For now, please use use software such as CrystalDiskInfo to see if there are any problem with your HDD. P.S. Windows 7 no longer receive update, consider use different OS.
|
|
|
I have an alternative idea, signature is automatically disabled on thread if the OP is newbie. That way, we don't need to restrict newbie account in any way. If it's genuine question, OP is more likely to get helpful answer since spammer aren't interested on thread where it's signature is disabled.
|
|
|
In the wallet, you can easily to as on-chain as cross-chain transfers. If you do it on-incognito side chain it's fully confidential.
Are there any article/example (whether non-technical/technical explanation) specific about it? This article explanation should be enough for you to understand I've read that, but it's not clear whether user could send pBTC to regular BTC address as easy and fast as sending BTC to BTC address and vice versa (send BTC to pBTC adddress). If user is required to exchange their pBTC to BTC before send it to regular BTC address manually or takes long time, then their claim (It's not a new #privacy coin, it's - a #privacy tool) is totally misleading/false.
|
|
|
|