A trivia, OP's username means "I like Japanese Porn"  As a member of the public, there should be a general elections whereby we are allowed to vote who will keep their place in the DTs!
Can you find ways to : 1. Prevent someone with multiple accounts have multiple votes 2. Prevent someone who wants to be (or stay as) DT from using money politics (buy someone's vote) 3. Make sure the election process can be proven fair without reveal any of users choice If you can't solve those problem, i'm sure the election will be disaster and DT condition will become even worse Most quality posts does not even receive any merits!
Then i should introduce you to this thread, Report unmerited good posts to Merit SourceI always this thread every few days and send some merit to reported good posts if i have merit left. |
|
|
|
The best answer would be to try it by yourself. Theoretically, it should be faster than CPU/GPU though. Personally I think OCL is fast enough to create an address/key pair. On top of that, we can use split key too. Loyce has a nice tutorial about this.
Why does it has to be split key? I see many ppl rent AWS to run vanitygen for normal key pair but never seen any private key get leak, are there really any incident that VM service stalk on ppl activity to steal key? AFAIK no, but most VPS services log some of users activity which raises some privacy concern. It's just a security practice and IMO better safe than sorry. Additionally by split key, even if your VPS got hacked, your full private key won't be leaked. |
|
|
|
How about this library https://github.com/BitcoinPHP/BitcoinECDSA.phpIt's specifically made to generate address, sign message & verify signed message which means the overhead should be little. I read the code a little, but i'm confused how to import private key and looks like they don't support Hierarchical Deterministic (HD) key. P.S. I never use this library and can't verify whether it's working, secure or/and work efficiently. |
|
|
|
Storage I/O speed and network connectivity usually are the main bottleneck on most cases. Computational power bottleneck usually only happen on barebone PC (which have few cores and .5-2GB) such as Raspberry Pi, at least on initial sync, not when on full nodes. Bitcoin core already use multi-core/thread for signature verification anyway & ASIC for hashing or/and signature verification only useful for initial sync as CPU should be good enough. IMO GPGPU / GPU acceleration is better and few core developer suggest it, but no one contribute to do it until now since it was suggested on 2013 ( https://bitcointalk.org/index.php?topic=3238.msg1451582#msg1451582) |
|
|
|
1. Dapatkah saya mentransfer BTC saya dari alamat SegWit ke BTC sebagai transfer BTC normal?
2. Apakah alamat dompet saya SegWit? dapat saya ketahui dan Bagaimana cara mengetahuinya?
3. Apakah ada perbedanya di mana saya memegang bitcoin seperti sekarang ini?
1. Bisa. Tetapi agan perlu memperhatikan apakah penerima menggunakan wallet yang mendukung alamat Bech32 SegWit. 2. Tinggal cek apakah alamat Bitcoin yang disediakan oleh wallet diawali dengan angka 3 atau huruf bc1. Ketika membuat wallet Bitcoin baru, biasanya aplikasi wallet akan memberikan pilihan SegWit atau Legacy (alamat address dengan angka awal 1) 3. Tidak ada SegWit adalah pembaruan protokol, bukan pembaruan Bitcoin Core. Bitcoin Core adalah apps/wallet/full nodes, tapi bukan jaringan Bitcoin itu sendiri. Seperti yang dijawab agan ETFBitcoin, upgrade ini berlaku ke jaringan Bitcoin, bukan spesifik ke Bitcoin Core saja. Ibaratnya ini memperbaiki jalan raya, nah jalan raya itu nanti bisa dipake oleh mobil panther (Bitcoin Core), sedan (Electrum), truk (Armory), yang mau melewati jalan tersebut, dst. Jadi bukan mobil panthernya yang diperbaiki, tapi jalannya. Saya malah ga paham maksudnya kalimat dalam perdagangan, profit seeking groups, NYC dst itu. Apakah kelompok gosip?
Mungkin yang dimaksud TheSoun04 adalah NYA (New York Agreement) dimana beberapa pool, exchange dan servis Bitcoin untuk mendukung SegWit. Tetapi NYA dipenuhi dengan drama dan menurut saya komunitas, miner dan developer Bitcoin tidak memiliki alasan untuk menuruti NYA karena Bitcoin bersifat decentralizedP.S. Penjelasan agan simpel dan mudah dimengerti  |
|
|
|
|
HEX/Hexadecimal is just a format to represent private key (or any data) while RSA is a type of cryptography. I don't see direct correlation between both of them.
As darosior said, you can convert or treat any hex private key as RSA private key, you just need to make sure your software accept HEX format.
But i think it's XY problem and you better tell us what you're trying achieve rather than tell how you try to achieve your problem/goal.
|
|
|
|
A new point-of-sale (PoS) app released by Zap allows merchants to independently accept transactions on the Lightning Network. Jack Mallers, the founder of Zap, described some of the properties of this new app on a recent Twitter thread. Mallers also spoke with Bitcoin Magazine to elaborate on some of the inner workings of the project. Full news : https://bitcoinmagazine.com/articles/new-zap-point-sale-app-enables-merchants-accept-lightning/
The device price will be slightly under $200, a bit expensive but the device included Bitcoin Core, BTCpay server and Zap (obviously) which allow merchants to have full control over their money and based on the preview on twitter, it have good UI and UX. |
|
|
|
i want to have the discussion in general terms not focused on Electrum, but for what it is worth the notification is not an unsolicited message that you receive from some server, it is you yourself doing the check for update but automatically and in the background. i explained how it works here https://bitcointalk.org/index.php?topic=5095856.msg49442064#msg49442064but basically it is you going to the official website and look to see if there is a new release. on top of that, the message you receive is signed with a bitcoin private key coming from 13xjmVAB1EATPP8RshTE8S8sNwwSUM9p1P which is hardcoded. so if the electrum.org website was compromised some day, you still wouldn't get valid responses when you check for updates because the key to that address also has to be compromised. Then it's similar with Alert System that Bitcoin Core used few years ago & IMO it's good solution for SPV wallet since the real risks are only private key of that address is compromised or the developer gone rogue. It's even better if Electrum Server also can share JSON message to users just in case the server is down or DDoS'ed. But it's not ideal solution for full nodes wallet/client due to similar reason why Alert System is abandoned. If this is implemented PLEASE add an option to disable it. This is only needed with insecure OSes that can't keep its programs updated.., its more nags to get out of the way, part of the bad habit certain OS users get into (so many nag windows they want out of the way without reading).
Don't worry, there's option to disable/enable it and user is asked to disable/enable it after install/upgrade Electrum. |
|
|
|
Silakan baca ulang poin dari OP berikut:
Saya sudah membaca dan memahami poin tersebut sebelum saya mengajukan pertanyaan, lalu kenapa walau sudah paham tetap saya tanyakan? Karena saya ingin tahu apa ada alasan lain selain poin tersebut Berdasarkan pengetahuan saya, tidak ada alasan lain untuk pertanyaan untuk kedua. Lebih tepatnya alamat SegWit-P2SH (yang diawali dengan angka 3) dikenali oleh hampir semua wallet, exchange dan online shop, kecuali wallet sebelum tahun 2012.
Sebenarnya saya disini masih terlalu awam untuk membahas dan mencerna pembahasan tentang Segwit, namun dengan karena keingintahuan saya tentang hal tersebut maka saya sepertinya harus mengetahui seberapa penting penggunaan SegWit ini.
Menurut saya, orang awam tidak perlu mengetahui SegWit secara detail, hanya perlu mengetahui kelebihan dan kekurangan SegWit saja Pada hakikatnya Segwit adalah pembaharuan pada sistem bitcoin Core yang dimaksudkan untuk mengatasi masalah pembatasan ukuran block sehinggan akan berguna untuk mengurangi kecepatan transaksi Bitcoin.
SegWit adalah pembaharuan/ upgrade pada sistem/jaringan Bitcoin, bukan Bitcoin Core, Bitcoin Core hanyalah salah satu aplikasi full nodes. Selain itu, SegWit berguna untuk meningkatkan kecepatan transaksi Bitcoin, bukan menguranginya. Hal ini dilakukan dengan cara membagi transaksi menjadi dua segmen, yang pertama dengan menghapus signature awal dari bagian aslinya dan kedua sebagai struktur terpisah pada akhirnya.
SegWit sendiri bermaksud untuk memberikan kecepatan tambahan dengan mengurangi ukuran signature pada setiap transaksi menjadi hanya seperempat saja yang harapannya adalah untuk membuat transaksi bitcoin menjadi lebih ringan dan cepat sehingga akan mempengaruhi harga fee transalsinya.
Lebih tepatnya ukuran dalam satuan weight yang menjadi 1/4, bukan dalam satuan byte. Agan bisa cek https://en.bitcoin.it/wiki/Weight_units jika ingin mengetahui satuan weight lebih lanjut. Setelah 1 tahun lebih SegWit diaktifkan, adopsi SegWit masih sangat rendah, hanya sekitar 40% meskipun SegWit menawarkan berbagai kelebihan. Semestinya hal tersebut mempunyai alasan mengapa persentase penggunaan SegWit masih dibawah 50% padahal yang seharusnya dengan kelebihan yang dimilkinya sudah bisa mendongkrak minat untuk menggunakannya. Ada beberapa alasan kuat menurut saya, seperti : 1. Ketidaktahuan Bitcoiner tentang SegWit 2. Kemalasan Bitcoiner untuk pindah ke wallet lain atau upgrade aplikasi wallet 3. Kemalasan developer ( wallet, exchange, dll) untuk mendukung SegWit 4. Beberapa miner, exchange dan wallet developer merupakan grup yang tidak suka SegWit Kelebihan SegWit yang dapat dirasakan secara langsung
1. Ukuran transaksi lebih kecil
2. Fee untuk transaksi menjadi lebih murah Saya pikir harus ada pengkajian lebih lanjut terkait dengan rendahnya minat terkait penggunaan SegWit ini gan sehingga adobsi SegWit ini akan mempunyai daya guna bagi semua orang yang mempunyai kepentingan dalam dunia crypto. Pengkajian mungkin perlu dilakukan, tetapi siapakah yang mau melakukan pengkajian? |
|
|
|
|
Single point of failure attack is serious cons, all attacker need to do either :
1. Take control over server to give malicious application or information
2. Launch DoS attack to prevent user know important update. This is really dangerous when it's combined with social engineering (such as fake update message few weeks/months ago)
3. User could be targeted specifically with MITM attack to perform another attack
Additionally, it brings false sense of security to regular users.
|
|
|
|
Lately I am reading few articles about Lightning Network. We know that for scalability, for cheaper transaction Lightning Network is a good solution. If I am not wrong then it is live in the Bitcoin mainnet.
Technically it's not on Bitcoin mainnet (except when you open/close channel), but you can use LN on Bitcoin mainnet today. What I understand is that installing the Lightning Network is extremely hard however I am considering to install and test one to see how it goes.
There are plenty information/guide about LN, so i'm sure it's not extremely hard. You might want to check this thread https://bitcointalk.org/index.php?topic=4940536.msg44524521#msg44524521So far I learned that the return of investment is huge for this. According to an article they made about $125 in a week on an investment of $2000 which was spreaded over 200 channels. It is around 5% a week which is not bad. They paid around $60 in transaction fees to setup all the nodes so they got it back in 3 to 4 days and after that all were profit. By the way that did not include the set up cost for nodes and the server cost. They had the Lightning Network with over 200 open channels. So far it sound very good to me.
Sounds bullshit to me, routing transaction fees on most LN nodes are very low (usually below 1 cents) Making your nodes have hundred of channel isn't easy unless you're merchant, have big coin capacity or you're the one who connect to other nodes (which mean you spend transaction fees). Additionally, if you set fees for transaction routing high, LN client could route through another nodes which offer lower fees. |
|
|
|
Berbicara tentang kecepatan dan transaksi Bitcoin yang lama dan cukup mahal tidak terlepas dari pembahasan dari ukuran blok Bitcoin saat ini yang tidak boleh melebihi 1 MB.
Sejak Agustus 2017, maksimal ukuran blok bukan 1MB, tetapi 4 juta weight (satuan ukuran). Intinya ukuran blok bisa sampai 4MB, tetapi pada umumnya hanya bisa mencapai 2-2.5 MB Masalah ukuran Blok Bitcoin, setelah saya baca dari beberapa literatur masih menjadi perdebatan diantara para developer Bitcoin dan belum menemukan titik temu.
Menurut saya, meraka tidak akan menemumkan titik temu atau sepakat karena ideologi yang berbeda
Reference : https://en.bitcoin.it/wiki/Weight_units |
|
|
|
Most of cryptocurrency exchange (such as LocalBitcoin & BTC-e) has always been centralized, but the difference are they didn't comply with KYC/AML, didn't ask personal information and allowed user with private connection. All anonymous (and centralized) exchange these days are scam or simply will be removed by the government soon. don, that is the problem i am talking about, there should be no problem that requires blocking of funds. When BTC is deposited it stays as btc and that is your money regardless of where it originated or who it used to belong to.
If you don't own the private key of your Bitcoin, then you don't own it Hopefully proper p2p stuff is going to get more robust and easier to use. Right now it's on the painfully clunky side.
And some DEX even require lock small amount of Bitcoin as insurance, but it should be more user-friendly if more people use DEX and atomic swap can be used securely |
|
|
|
I'm not expert or fans of LN so i can't answer all question 2. It looks like the most efficient evolution is a network where everyone connects with only a few, big, stable nodes?
On LN? Yes & it already happen naturally as merchant/seller usually become "big" nodes. 3. What happens if everyone wants to get their bitcoin out of the network at the same time?
If you meant LN network, then main-chain will be flooded with transaction about closing LN channel 4. What happens if the big nodes decide to just go offline??
There's no thing such as big or small nodes. If some nodes are offline, bitcoin network will run just fine. But if you're talking about LN nodes, then user funds are locked for some times and there are 2 possibility with transaction routing : 1. User simply route their transaction through another nodes/channel 2. User is forced to make new channel 6. If the Lightning Network ends up being what everyone uses, who will use the main network? Also, does that mean that mining might be impacted?
You still need main network even if everyone use LN. You still need to create on-chain transaction to open and close LN channel. 7. If block rewards keep reducing but transaction volumes don't increase, will that impact mining? Or is the idea that fees will high enough to pay miners? Does this also assume that the value of Bitcoin must be high?
The scenario you mentioned is possible, but if both don't happen then mining difficulty will drop when block rewards decreased |
|
|
|
Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far?  Why would you run it online? It is risky to do that because your data could be intercepted. You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me. I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem. Using split key is a much better solution, so that Google itself can't know your private key either. They can still know you generated the address through. I totally forget about split key. But google knowing user generate vanity address doesn't matter unless you could know bitcoin address just from partial private key, brute force to get private from an address with partial private key or have serious privacy concern. |
|
|
|
Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far? Why would you run it online? It is risky to do that because your data could be intercepted. You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me. I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem. But Google's TPU is optimized for AI stuff (deep learning, neural network, machine learning, etc.). |
|
|
|
|
Android file system don't use NTFS or FAT/FAT32, most devices uses ext4 so you should select "ext2, ext3,ext4, ufs, ufs2, etc.", otherwise you won't able to find your wallet files or other data you have.
You also need to know where the wallet keep wallet file, but most times it's placed on Android/data/<application directory>
|
|
|
|
|
Show Posts
