My thought on Proposal I :It's not bad idea if there's no changes on available features (avatar, signature, etc.) for existing ranks, even though it might confuse some member. You might want to suggest what available features on suggested ranks. My thought on Proposal II :I disagree, that would restrict freedom for people who isn't newbie on bitcoin/cryptocurrency world, but just joined this forum. Example : Member warith joined this forum to share critical vulnerability of Coinomi wallet at WARNING - Coinomi Wallet CRITICAL Vulnerability Made Me Lose My Life Savings, if he only can post on (Board of Children Newbie Discussion), many members won't know about it.
|
|
|
|
FYI, Coinomi made official response regarding this matter at https://medium.com/coinomi/official-statement-on-spell-check-findings-547ca348676b. It doesn't like official statement, especially on this part The spell-check requests that were sent over to Google API were not processed, cached or stored and the requests themselves returned an error (code: 400) as they were flagged as “Bad Request”¹ and weren’t processed further by Google²
They act like they know how Google API works or simply assume Google API discard all bad request even though only Google engineer who knows Google API's behavior. While i doubt it's the reason Warith's coins is stolen, it clearly shows that they're not being professional or try to blame Warith instead. Glad i stopped using Coinomi after they decide made their wallet closed-source. |
|
|
|
Some one grabs private key for address ABCD can he go after address EFGH?
No, unless your master public key also grabbed and your wallet generates non-hardened address. Most wallet generates hardened address, so you don't need to worry about this problem. If your wallet don't use seed/HD derivation/mnemonic, you don't need to worry about it unless your wallet uses bad random method. I am under assumption that second address EFGH has a completely different key and can not be attacked with the private key from the first address. Correct?
Yes |
|
|
|
Mainly because it's a company and the fact they run funding where people think blockstream must have some private agenda or they use LN to centralize bitcoin and take profit so they can paid their investor. But the fact are : 1. Only fraction of Bitcoin developer work at Blockstream 2. Even if Blockstream were to defunct, Bitcoin and Bitcoin Core development won't be stopped as there are thousand contributor worldwide This article isn't 100% accurate, but it sums up this topic : https://medium.com/bitcoin-not-blockchain/the-blockstream-conspiracy-and-the-bitcoin-cash-pump-8f35fb44491a |
|
|
|
You can manually choose Electrum server so you can broadcast your transaction. There are few website which provide such list such as https://uasf.saltylemon.org/electrum and https://1209k.com/bitcoin-eye/ele.phpI don't remember which Electrum version used by your Tails, but if it still using version 2.x.x, you should upgrade since AFAIK Electrum 2.x.x have problem connecting to newer Electrum server. |
|
|
|
|
I doubt such mistakes would happen repeatedly many times, especially most wallet preview transaction before send/broadcast it.
It's more likely newer version of ETH wallet is buggy or someone with connection to the pool try to see community/government reaction.
Additionally it's poor way to laundry coins since :
1. It raises attention
2. If you use pool, you leave many information which can be used to track you (IP, hashrate, browser fingerprint, etc.)
3. Anyone still can trace your coins movement since the link isn't broken or obfuscated
|
|
|
|
|
Why don't you use HLTC or bitcoin's timelock (CSV, CLTV, nLocktime or nSequence) which already exist and can be alternative to your idea.
Also, there are 3 important questions :
1. Assuming a transaction is reversed, that means blocks would become invalid since it's hash (along with all next blocks) will become invalid. How do you plan to solve this problem?
2. Attacker might able to steal private key after user make a transaction from special address, how do you plan to prevent this accident?
3. How do someone veto a transaction which made by attacker where we can verify who's the owner/attacker without compromise owner privacy?
|
|
|
|
Reddit's threaded structure tends to water down discussions, splitting them up into numerous sub-discussions, as well as making it harder for the reader to easily read through a topic. It's upvote / downvote based comment and topic sorting and filtering essentially introduces censorship by democracy - unpopular opinions get pushed down and filtered out, while regurgitated popular opinions consistently get pushed to the top. I'm not particularly fond of Reddit's social media like site design either.
I agree, even though AFAIK there's sub-reddit option to remove downvote option. As for quality:
1. less strict moderation
2. spam eradicated
3. not spending massive amounts of money and effort on numerous staff, machine learning based detection systems, etc.
Pick 2
By removing signature and bounty child board, 3 of them can be achieved (or partially achieved) at cost forum activity significantly decreased. Using Machine Learning to detect spam sounds good even though it's expensive, but it's possible if deleted posts because spam is preserved as training data, there's category option when report post and few people with such expertise. I'm not sure where to discuss Lightning - would Bitcoin discussion be a good place? I want to start to use it to accept payments.
Not bad idea if you self-moderated the thread. You also can check https://bitcointalk.org/index.php?topic=4638321.320, but it's technical oriented discussion rather than general discussion |
|
|
|
i guess it's not mandatory we can skip it?
Yes, in fact there's no mandatory update, but only critical/important software update. Just hope you won't encounter one of bug which fixed on newest version. so i have the "unknown rule" msg i can ignore it i suppose Yes. Most of the times that means you're using older version of Bitcoin Core or block mined with AsicBoost. But IMO it's still better to update your Bitcoin Core |
|
|
|
Bitcoin & Cryptocurrency Technologies by Jameson Lopp also great read and it's available for free at https://lopp.net/pdf/princeton_bitcoin_book.pdf. The book was released in 2016, so it's a bit oudated. If you want to go deeper, you should know that it is not going to be easy if you don't have good knowledge of: computer science, programming languages, networks, networks security, cryptography...
Don't forget game theory  |
|
|
|
The quote of 2^96 represented how many potential PRIVATE keys would work for a single PUBLIC key if they were evenly distributed (not how many total private keys were there).
296 katanya kalo dihitung pakai prinsip lubang merpati* *ane gak paham dan gak ingin mempelajarinya lebih jauh, mungkin bisa tanya atas ane saja. Edit: kok kayaknya cuman 256-160 = 96 lol Saya juga kurang mengerti tentang hal ini, tetapi seharusnya bukan 2 96 karena : 1. Dari sebuah private key, kita bisa membuat 2 jenis public key (compressed dan uncompressed) 2. Karena hal 1, sebuah private key bisa menghasilkan 2 bitcoin address (dari 2 public key) 3. Tetapi bitcoin juga memiliki P2SH dan Bech32 address 4. Selain itu, Bech32 dibagi menjadi 2 yaitu P2WPKH (dengan panjang 20 char) dan P2WSH (dengan panjang 32 char) Referensi : 1. https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki2. https://en.bitcoin.it/w/images/en/4/48/Address_map.jpg |
|
|
|
apakah ini berarti ada beberapa pasangan Private key yang Mengarah Ke 1 Address Yang Sama?
Ya, tetapi kemungkinan tersebut sangat kecil [1]Atau Ada Beberapa "Angka Spesial" Dimana Beberapa Privkey Yang Berbentuk Heksadesimal Tidak dapat Menghasilkan Suatu Address?
Benar, ada beberapa private key yang tidak bisa di konversikan ke public key/address. Lebih tepatnya hanya private key antara 0x1 sampai 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140 saja yang valid[2]Referensi : 1. https://bitcoin.stackexchange.com/a/312. https://en.bitcoin.it/wiki/Private_key#Range_of_valid_ECDSA_private_keys |
|
|
|
I'm pretty sure those are bitcoin addresses, not public key since public key and address uses different format [1]There are 2 types of public key which are compressed and uncompressed and i think that's the problem/reason you got different bitcoin address from what you expect. But i didn't read the code, so i might be wrong. Reference : 1. https://en.bitcoin.it/wiki/List_of_address_prefixes |
|
|
|
|
After read your idea and do few research, i think it's good idea. Here are my opinion, comment and suggestion :
- It's hard to determine distance of blocks which is safe enough or last known "safe" block (at least without visit cryptocurrency news, forum or community)
- Determining "safe" distance of blocks automatically by wallet is extremely important, otherwise only users who check news or/and some technical knowledge who can enjoy the benefit
- It's not really useful for user with SPV wallet/nodes who never check news due to SPV wallet/node vulnerability
- Assuming intentional hard-fork happen and forked coin "created" (which don't have replay protection) very recently, transaction is still vulnerable to replay attack since wallet might choose hash before hard-fork
- Unless you use SegWit script versioning, hard-fork is needed. But if you use SegWit script versioning, only user with upgraded client would enjoy the benefit
- Flash_back_block isn't needed since i doubt there are 2 or more block with same hash. Even if Flash_back_block only contain 12 char of hash from right side, there are 2.814749767x1014 combination. There's no problem with searching hash with it's block height as bitcoin client already use block indexing
- For intentional hard-fork, forked coins could use sighash as replay protection which save user time
|
|
|
|
some mining pools will mine your transaction for you if you pay them. viabtc has this service. it takes tx id as input thought. you could try broadcasting via the tool on their site. it may accept zero fee transactions. if it does it'll return a tx id which you can use. another one is btc.com: https://pushtx.btc.com/AFAIK most free transaction accelerator can't/don't accept transaction with low fees or transaction which isn't exist on their pool While it's possible to "bypass" default minrelayfees with paid transaction accelerator, it's ridiculous idea as you'd pay more than 192 satoshi (1 sat/byte for common transaction) and risking de-anonymization. |
|
|
|
|
What you need is "Right to be Forgotten" to make sure your images/information is removed from this forum. I doubt plagiarism as reason gonna change moderator mind.
The real problems are such right only recognized on EU and few others country & this forum don't bother with it (GDPR, AEPD, etc.)
P.S. i don't know OP history at all
|
|
|
|
|
Saya setuju dengan pendapat agan
Cryptocurrency tidak akan pernah sukses dalam jangka panjang jika semua orang hanya menggunakan cryptocurrency sebagai "emas", komoditas ataupun investasi. Jika fungsi cryptocurrency seperti mata uang, metode pembayaran atau smart-contract yang bebas & tidak terkontrol diabaikan atau tidak dipedulikan, cryptocurrency hampir tidak memiliki manfaat positif dan lebih baik dilupakan saja.
|
|
|
|
Which tools you used? If those tools are updated before August 2018, most likely it doesn't work because they don't support parse block/transaction contain/use SegWit. Have you tried https://github.com/alecalve/python-bitcoin-blockchain-parser, https://github.com/chainside/btcpy or https://github.com/bitcoinjs/fast-dat-parser? all of them are updated after August 2018 and 2 of them claim to support SegWit ? I never use it, but it already support block/transaction contain/use SegWit. But how to parse those files? I really want to know the answer!  Aside from using tools/library, your only choice is learn about LevelDB (where as Bitcoin Core have it's own fork/version of LevelDB) and find out how Bitcoin Core use LevelDB then write your own tool/library |
|
|
|
|
Pertanyaan ini cukup ambigu karena kita tidak tau jenis cryptocurrency yang dibahas ataupun medium sebuah fiat.
Tetapi sudah jelas bahwa fiat (uang kertas dan uang logam) memiliki tingkat anonymity yang lebih tinggi karena :
1. Tidak ada sejarah/catatan transaksi dari sebuah uang kertas/logam
2. Dalam cryptocurrency, ada banyak hal yang harus diperhatikan supaya aktivitas finansial tetap anonim seperti koneksi yang aman, menggunakan identitas anonim, dll. Sedangkan dalam uang kertas/logam, seseorang hanya perlu mencari cara supaya tidak ada sidik jari/fingerprint di uang kertas/logam tersebut
3. Pihak ketiga tidak akan tau siapa yang pernah menggunakan sebuah uang kertas/logam tanpa memiliki uang kertas/logam tersebut
|
|
|
|
|
Show Posts
