My ledger device can't be connected to the Wasabi wallet, I had many times disconnect and connecting USB cable and I was set up my device also, but still, the wallet won't detect my device.
some information:
- ledger nano s
- firmware version 1.5.5
- wasabi wallet version 1.1.12.2
is there I missing something? my ledger just worked fine using electrum and ledger live.
According to patch note ( https://github.com/zkSNACKs/WalletWasabi/tree/v1.1.12.3), the problem is fixed on Wasabi 1.1.12. 3But if you still face error, you could open Logs.txt to diagnose the problem, it's located on |
|
|
|
|
The idea would be slightly better if it's changed to "Create silver and gold version of Copper membership", where the one who bought it get similar benefit compared with Hero/Legendary user, except signature part.
|
|
|
|
BUT a one time block size increase to 10MB, and with current Bitcoin on-chain usage keeping those blocks full, would make each node process 10 times the data, and make it look exponential.
People call it linear growth or O(n) |
|
|
|
how do I make sure nothing happens between the transfers...like having to go online with my seeds and so forth?
Electrum have good guide about it to without going online with your seed, see https://electrum.readthedocs.io/en/latest/coldstorage.htmlYou need two device and a way to transfer the unsigned transaction. |
|
|
|
but constantly building and destroying offline machines for signing sounds like a lot of work.
Each party uses a fresh Live Ubuntu to recover her wallet using seeds and then signs the transaction and terminates Ubuntu. Does it make sense in terms of security? 1. Do you verify the whether ISO is genuine? See https://ubuntu.com/tutorials/how-to-verify-ubuntu2. AFAIK Ubuntu doesn't have built-in Bitcoin wallet software, so my first question also apply to the Bitcoin wallet software used 3. What medium do you use to transfer unsigned transaction? Internet is a bit risky. P.S. Using Tails is a bit more convenient (since it include Electrum) and protect your privacy if you need internet connection. |
|
|
|
|
Additional information could make recovery process easier,
1. Do you remember what software you used to generate the words seed? While most wallet uses BIP 39 standard, Electrum have different word seed standard
2. Do you have the wallet file created by wallet? It could be used to extract address to make recovery process faster
|
|
|
|
For something awful to happen, all of them (and many others) would have to turn a blind eye and go rogue around the same time.
Additionally, Bitcoin protocol need both miner and node. So if it happened, it will cause hard-fork (unless the software still follow Bitcoin protocol and perform covert attack such as preventing specific transaction included in block) while Bitcoin network itself is halted because there's no block mined. Then it's just matter before miner find out about it and fix their system. |
|
|
|
Okay I just installed Ruby but can someone confirm exactly what code I should save in the "ruby your_file_name.rb" document if my private key is: ef242kfjj24ekf3223jesdkhefsfhk324wuefhw38fhrypofhtr34d342132d34jsd01 ?
If your private key length is 66 and end with 01, then you need to change these line privatekey = "0351764dc07ee1ad038ff49c0e020799f0a350dd0769017ea09460e150a64019"
extended = "ef" + privatekey + "01" # you can remove 01 to make your wallet generate uncompressed public key
into privatekey = "ef242kfjj24ekf3223jesdkhefsfhk324wuefhw38fhrypofhtr34d342132d34jsd01"
extended = "80" + privatekey
Are you sure notepadwif.rb file is located on ~ ? |
|
|
|
Correct me if I'm wrong, but iOS wallets pretty much technically run natively(by default without iOS devs updating their apps) on the Apple M1 MacBooks, right?
Oh, you’re right. Any iOS wallet should work perfectly fine. One is not able to resize the application window, but that’s a minor inconvenience. It would be interesting to see Electrum on iOS which could behave like a full-fledged client once it is launched on any M series CPU. Still, there are plenty of other wallets to choose from. I would choose BlueWallet since Samourai is not available on iOS yet. It looks like some apps might not be available for download from the store on the M1 powered devices if developers decide so. Python 3.9.1 can run on M1, even though it's on experimental stage. So it's possible Electrum already can run on M1, even though i have doubt about PyQt since it's binding to low-level library. |
|
|
|
|
It's impossible since miner would choose transaction with higher fee rate and in first place, i doubt it can be broadcasted. Either cancel it with higher fee or hopefully it's dropped from mempool (not recommended).
|
|
|
|
It seems that Ledger has no intention of making the secure element fully open-source.
Now that i know there are open-source secure element, why don't Ledger migrate from closed-source to open-source secure element? Do they find secure element they currently use is more secure than all open-source secure element? |
|
|
|
People who learn technical side of Bitcoin (or P2P system in general) already know there's no single solution for scaling problem, even LN have 2 main disadvantage, 1. LN is only meant for micro-transaction 2. LN only useful if you make transaction regularly (at least more than 2 transaction within channel duration) As for solution on base-layer, there are few option, 1. Schnorr signature 2. Using different number representation on transaction/block (e.g. Increase block size (5%) by using CompactSize instead of UInt) 3. Just increase block size based on lowest growth of computer hardware and internet speed on 3rd/developing world country. but elsewhere, you can hardly get a 1mbps line with very limited monthly quota
It's naive question, but how limited is the monthly quota? 100GB? 10GB? or just 1GB? I can't even propagate a 1MB block in a timely manner.
Actual block propagation uses compact block (where it's size only few KB) though |
|
|
|
If, and it is a big IF, bitcoin client was not such a mission critical software with so many considerations and requirements including and not limited to avoiding unintentional chain splits we'd have seen at least two or three major rewrites and at least 3 or 4 competing pieces of software.
Although I haven't gone through each of the following to know how many of them are actual rewrites of the protocol but we already have at least a dozen full node implementation of bitcoin that can also be found on the P2P network. To name a few: 1. Gocoin2. Bcoin3. libbitcoin node4. Parity bitcoin5. BTCD6. Stratis7. bitcore8. rust-bitcoin(double check the links, I may have copied a wrong one here). And there are many more, 1. Bitcoin Knots ( https://bitcoinknots.org/) 2. therealbitcoin http://therealbitcoin.org/) 3. Wire ( https://github.com/btcsuite/btcd/tree/master/wire), which is part of BTCD now 4. Bitcoin parity ( https://github.com/paritytech/parity-bitcoin) 5. Multichain ( https://www.multichain.com/) 6. Several bitcoin core fork aimed to realize softfork/hardfork in past (Bitcoin Unlimited, Bitcoin ABC, etc.) MIT license is not issued by MIT to projects! it is a license that originated at MIT and it simply defines certain terms and conditions for open source software that anybody can use.
And there are few variant of MIT License template, even though mostly it's based on Expat License. |
|
|
|
|
Check whole code of open source software? No, but i take a peek at few Python software (e.g. Electrum and Bitcoin library).
On a side note,
1. When security is important, i avoid unpopular open source software, unless someone publish proper audit.
2. The question also applies to dependency of open source software you use & any cryptography used.
|
|
|
|
The answer is simple, it's because people feel more secure or other ridiculous reason (e.g. computer hardware will grow faster than ever). Which one did you use to generate your wallet? You would have no choice but to check them all, one by one. This way, we're making the attacker's brute forcing easier too, not just ours. As far as I've seen, checksums on mnemonics are useful only on brute forcing, because on seed validation you must have written the right words. Even if you've written a wrong word or anything else, how exactly would you get your funds back? Where is checksum going to help? Checksum help people to recover mnemonic far faster with very few missing words (as long as it's not last word). You don't need to generate many things (seed, private key, public key & address) to check whether you generate correct mnemonic. Besides, if attacker already know some words of your mnemonic, that means the attacker already breach your device/home & you have bigger problem to worry about. |
|
|
|
and a list of trustworthy wallet providers for these Alt coins?
I think this script ( https://github.com/ymgve/bitcoin_fork_claimer) is what you're looking for, it support various altcoin, but it uses Python 2.7 (which reached EOL/end of life) and only have CLI/terminal option. Electrum fork for these altcoin is an alternative, but you need to verify the source code or trust the developer. I reckon most people has already forgotten about these coins and they just destroyed the wallets. (I hope not)
Or they don't care because they don't have much Bitcoin or the value of the altcoin is too small for them. There's also privacy concern from sending to same address (exchange in this case) or make single transaction with all your addresses. |
|
|
|
Not research, but apparently Electrum uses JSON to store the wallet content. But obviously it's not efficient since it's written on pure Python and JSON doesn't scale well. There's discussion about JSON alternative for Electrum at https://github.com/spesmilo/electrum/issues/4823, you might find one or two interesting idea. For example, Bitcoin Core currently uses LevelDB for the UTXO set and all indexes (block index, transaction index, block filter index). Berkeley DB and SQLite (in 0.21 for descriptor wallets) are used for the wallet.
Are there any particular reason why Bitcoin Core uses Berkeley DB & LevelDB while both of them are key-level database? I imagine it's easier to maintain Bitcoin Core source code if only one of the is used. |
|
|
|
Don't worry OP, absolute decentralization is impossible, there are ways to perform take over on every decentralized system. But your reasoning aren't related with decentralized system weakness. 1. The lack of authority from the crypto founder to resolve issues from its user. We will not talk about the authority coming from the government because many of us here will not agree of them to interfere in the system because they can just ruin the anonymity by conducting KYC and other preventive measures. So, what I am seeing is the lack of addressing problems from the founder of the crypto. After they implemented the system they will just say that system is good and ready to go and if you as a user will get mistake then that is your problem and your fault. No one had force you to join in cryptocurrency and you must adapt to it. This is not good for those who wishes a better system.
There are ways to resolve on issue on protocol level without authority. 2. Miners service are decentralize.
Who would ever thought that they could get you a 1$ transaction of a fee which could be more than a thousand dollar's fee? There is something wrong and miners should be held liable into this by only limiting the transaction fee to be deducted not more than the transacted amount. They are abusing due to the fact that their service is in demand especially the bullish trend of bitcoin.
Transaction fee rate is based on demand and supply, you can set low fees at risks of waiting longer for the transaction got confirmed. Transaction fee itself is exist to prevent spamming transaction. 3. The abuse may be only happening and will be resolve between both parties. Same thought about in number 1 but this talk about resolution between both parties and not about the lack of authority from the founder. A certain user could mistakenly send high amount in the transaction without checking it and will be requested for a refund. The other party could deny and there us nothing you could do because it was your fault and no one can help you.
It's user mistake, even on centralized service refund could took long time, cost you refund fee or the authority simply reject your refund request. 4. Complete decentralize platform may gone wrong.
Again, there is no perfect system and if there will be errors that will going to take place expect that you can no approach any technical team to resolve the issue. Reminders that there are no technical team to review in that errors but only the forum provided.
If you mean error on protocol level, decentralized system could upgrade their network to fix error. |
|
|
|
If you import 12 words, you might need to tick option "BIP 39 seed" after clicking button "Option" when you enter 12 words. If you import private key, you need to use prefix "p2wpkh-p2sh:", example p2wpkh-p2sh:[Your private key]
|
|
|
|
|
Show Posts
