I know... I guess electrs will take the lead But last time I checked electrs was very bad at handling mempool transactions... any other electrum server implementation besides electrumX or electrs?
The only other one I know of is "Electrum Personal Server" aka "EPS"... might be worth a look?  Also, what exactly do you mean by "very bad at handling mempool transactions"? I've not had too many issues with it, but I'm not trying to do anything really extraordinary with electrs... basically just letting it run off of a standard Bitcoin Core node and connecting to it locally from my personal copy of Electrum... |
|
|
|
The other question is why the creator kept private keys, and do those pr. keys belong to the physical coins.
Did he keep private keys those? As far as I can tell, the download at mega.nz was simply a list of all the generated "addresses": 1. Download full list of generated addresses for Series 3 from this link: https://mega.co.nz/#!fcsGRRYK use thes key provided by us to download the file. The private keys were (quite rightly), only printed and "stored" on the physical coins themselves... underneath the security holograms: HOWTO REDEEM THE COIN
=======================
1. Peel off the security hologram of the coin
2. Read and copy QR code of the printed paper under the hologram, this is the encrypted private key of your coin (begin with ‘6P’).
It seems the OP here has the Address List... and the "passphrase" list for decoding the BIP38 encoded private keys... but doesn't have access to the private keys from the physical coins themselves. Essentially, OP has found a keychain with a whole bunch of keys on it... but doesn't have the "locked boxes" that these keys actual unlock  |
|
|
|
I remain skeptical that there’s at least one person who would give up his/her cut of heritage only for the reason of screwing others unless his/her portion is "penny"-worth. And then, we’re not talking about strangers but of heirs who are supposed to be related. If their cuts are equal they are supposed to sign transaction.
You'd think this would be the case... but I've personally seen the results of "estranged" relatives fighting over property/funds etc. following deaths and marriage breakups etc. It ain't pretty and sometimes people do very irrational things to cause other people pain.  (have you had a read through the reputation board lately? ) Obviously, it's not guaranteed that this will happen... it's just something to consider when going for an n-of-m multisig, where n==m... It only takes one keyholder to either lose their key, or refuse to sign, and the funds are effectively unrecoverable. |
|
|
|
May not get any answers due to the ElectrumX dev committing to BSV, but have you tried logging an issue on the ElectrumX GitHub? (or maybe the fork of ElectrumX that is still supporting BTC) |
|
|
|
Is it that?
No... bitcoind is the Bitcoin Core daemon... basically the "server" component that runs in the background. I asked because I wanted to know if the rest of it had actually compiled properly. "bitcoind" seems to have been built "OK", so if "bitcoin-qt" is not being output in the "src" folder along with "bitcoind" and "bitcoin-cli", then it would appear that your compile didn't actually work properly (unless you told it to build without the GUI... Did you use --without-gui with "configure"? ) In any case, you'd need to look at the actual output from make to figure out why "bitcoin-qt" has not been built... Because when I command that, this happens:
The error you're getting is because you've already run a later version of Bitcoin Core at some point which has upgraded your wallet.dat which will be in your "~/.bitcoin/wallets" folder... rename/move the existing wallet.dat and then try starting "bitcoind" again. NOTE: bitcoind does NOT have a GUI... so once "bitcoind" is running, you will need to use "bitcoin-cli" from the command line to interact it. |
|
|
|
After compilation of v0.16.0, is there a file called "bitcoind" that has been created anywhere? |
|
|
|
No need to have all 3 in one hand to distribute the fund.
DUH! Yeah... Of course, it's multisig, one person creates the transaction distributing funds evenly, and then everyone else signs it... However, I guess the opposite scenario is also true... if one party feels like being a complete ass, they can actually prevent everyone from getting any money by refusing to sign the transaction with their key... and before anyone says "why would someone deliberately sabotage their own chances of getting money by refusing to sign?"... trust me, I've seen people do a LOT worse out of pure spite |
|
|
|
|
It's possible there is some data corruption in your Bitcoin Core data, that is causing issues for Armory... So, you might need to "reindex" your Bitcoin Core to see if it can fix it... but that will likely take quite a while to complete.
|
|
|
|
will that message be equal with the message from armory?
It's not the "message"... but the "signature" that you need to worry about... and chances are that the signature created for an identical message in a different wallet will actually be different (sometimes even if you sign the same message twice in the same wallet) due to the "random nonce" used when creating the signatures. Message signed in Armory: -----BEGIN BITCOIN SIGNED MESSAGE-----
HCP Test signing a message in Armory and Electrum
Date: 2020/08/20
-----BEGIN SIGNATURE-----
1FFv3G8N1XLGrYcz1QeU8tA4KPCzWGjAJh
G1kswQr0+uoeNYWwb8wxz4tiGSjpU8R+VGxldtdxrNckM0YYe4Pm9u8F+sKvm3iAJCQGUvL4hQejAEyw6xx+f9M=
-----END BITCOIN SIGNED MESSAGE-----
-----BEGIN BITCOIN SIGNED MESSAGE-----
HCP Test signing a message in Armory and Electrum
Date: 2020/08/20
-----BEGIN SIGNATURE-----
1FFv3G8N1XLGrYcz1QeU8tA4KPCzWGjAJh
HEguJMI9sQVEIDwR80pMzSq4GetnE5eaRGCOUDhPPv+ZS8JmwGicbHHH04qtVdPBTHFI3rKL/qvJcLwCe4xlM84=
-----END BITCOIN SIGNED MESSAGE-----
However, even though the signatures will be different, anyone will be able to verify that they were still signed by the same address/private key |
|
|
|
This would result in the circumstance that the BTC always need to be in the multisig wallet.
For OP to actually use the wallet he either needs
1) a "backup" of the private keys everyone has to actually access the funds or
2) a 3 out of 6 multisig with him having 3 keys.
Both is extremely impractical because he basically just has a single address to use.
The previously mentioned approaches are better in terms of privacy. OP can use as many addresses as he wants without affecting the security of the backup mechanism or his privacy when transacting.
I see downsides of your approach, but don't see any upside.
That's not exactly true... It wouldn't need to be 3-of-6. If the OP was using Electrum, they could create a 3-of-3 MultiSig wallet... using 3 seeds... instead of using 1 seed + 2 pubkeys. That way, their copy of the wallet would have all the private keys needed to be able to create/send transactions. It would be akin to having a "disabled" 2FA wallet. OP could then give 1 seed to TrustedPersonA, 1 seed to TrustedPersonB and have 1 seed in Will. On death, the parties can then use the 3 seeds to recreate the wallet. In the meantime, the OP could use the wallet as they wanted for everyday use... it's still an HD wallet, so OP would get new addresses etc. And wouldn't look any different to any other P2SH type wallet really. Granted, the OP would need to keep backups of all 3 seeds, but that's not really any more difficult than keeping a backup of 1 seed from a "standard" wallet... you're effectively just storing 36 words instead of 12  The big problem I see with all of this... is the final distribution of funds. If all the funds are in one wallet, the party that gets all 3 seeds "first" could effectively take it all. |
|
|
|
Now before I try that I would like to clarify something and tell me if I'm wrong. Bitcoin network "doesn't" exist. There are just some people running full nodes with some ip addresses and a port that share with other full nodes. When you install bitcoin core you have some default nodes that you follow (I think they're written on a txt file).
No, they're hardcoded in the code, specifically in chainparams.cpp... they're the "DNS Seeds": vSeeds.emplace_back("seed.bitcoin.sipa.be"); // Pieter Wuille, only supports x1, x5, x9, and xd
vSeeds.emplace_back("dnsseed.bluematt.me"); // Matt Corallo, only supports x9
vSeeds.emplace_back("dnsseed.bitcoin.dashjr.org"); // Luke Dashjr
vSeeds.emplace_back("seed.bitcoinstats.com"); // Christian Decker, supports x1 - xf
vSeeds.emplace_back("seed.bitcoin.jonasschnelli.ch"); // Jonas Schnelli, only supports x1, x5, x9, and xd
vSeeds.emplace_back("seed.btc.petertodd.org"); // Peter Todd, only supports x1, x5, x9, and xd
vSeeds.emplace_back("seed.bitcoin.sprovoost.nl"); // Sjors Provoost
vSeeds.emplace_back("dnsseed.emzy.de"); // Stephan Oeste
vSeeds.emplace_back("seed.bitcoin.wiz.biz"); // Jason Maurice
These are what a node will attempt to connect to when they have no known peers... and they'll redirect the node to peers to try and connect to. If I remove that txt file and change the ports (plus some changes on the difficulty because it's too high) then everyone that will download my altcoin core will have a different blockchain to mine right? (satoshi's genesis block will remain, and I really don't care for that)
You can't just remove that file... you'd need to modify the source code to use your own DNS Seeds... if you just removed them from the source code, chances are that you'll face issues with other parts of the code that relies on them being populated with something meaningful. If you don't have any "DNS seeds", then anyone that would attempt to use your altcoin, would not be able to connect to the altcoin network unless they already knew the IP address/port# for a node already on the altcoin network. So they wouldn't receive any block or transaction information... and you would effectively have no network... Finally, I'd suggest you ask your questions regarding that guide... in the thread for that guide!  |
|
|
|
I just need an easy to use phone/android wallet to use that lets you scan QR codes to send money to. I was using blockchain.com's wallet and it's fine enough but I keep getting requests to use segwit and that seemingly doesn't use them. Does anyone have any recommendations of ones that can do this???
If you are just wanting to transact using Bitcoin, and QR codes is important, then I would suggest either Electrum or Mycelium. The UI on Mycelium is subjectively better/easier... but I personally think Electrum is a better wallet. Both support SegWit addresses. |
|
|
|
so i have already only 12 word seeds but its cut into two txt file
It would appear that it was either a poor attempt at trying to "secure" the 12 word seeds by cutting them in half and storing the halves separately... or perhaps they were copy/pasted badly out of a spreadsheet or off a website in groups of 6 rather than all 12 at once? but the 6 word is longer than the 12 word and there is difrent in the last word of 6 seeds ?
not sure exactly what you mean by this... do you mean that the number of lines in 6 word file is longer than 12 word file? I would expect that it should be twice as long Are you saying that some of the words in the 6 word seeds, aren't the same as in a 12 word seed? for instance: 6 word: foot ears india flow fell row12 word: foot ears india flow fell hungry grow great level pill outer major |
|
|
|
In a similar line of thinking... is there any sort of "email" that might be associated with these 6 word passphrases that you could try using with Warp Wallet ( https://keybase.io/warp)? I tried the 6 word phrase that you gave earlier ( child shout iron pair row aunt), but it didn't generate the correct address:  |
|
|
|
How much experience have you had in the past with coding/compiling on Linux based systems? 0 Well... I guess you're not doing too badly for someone with zero experience! But it does explain a few things. Note, I'm not sure that diving headfirst into attempting to compile Bitcoin Core as your "first project" is the best way to learn the in's and out's of compiling on Linux But we'll take a stab at it. Essentially, run configure and see what it tells you is missing, then do what you need to fix that issue... at this point, it seems that simply executing ./configure with the appropriate settings as per the output from building the BerkeleyDB libs should fix your current problem. I'd expect (assuming that you already installed all the required libs and dependencies here: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#ubuntu--debian) that it would complete without error and you should be able to use make |
|
|
|
For starters, you ignored the message given here:  It said that you needed to run the "export" and then then "./configure" commands to set the BDB_LIBS and BDB_CFLAGS values... you didn't. Which then meant that when you attempted to run the ./configure as part of the build process... it failed here:  With the error saying that it could not find libdb_cxx headers. From the video, it seems that you are just copy/pasting commands from the build-unix.md instructions without fully understanding what they are meant to be used for, nor which ones you actually need to use. You're not meant to use every single command... some of them are for specific setups/configurations etc. It also seems like you're not really reading/understanding some of the output and what it means either. How much experience have you had in the past with coding/compiling on Linux based systems? |
|
|
|
Are you running Bitcoin Core with the server=1 option (either on the command line or in your bitcoin.conf)? The "connected" in Armory being in Purple means that it is not communicating "properly" with your Bitcoin Core node... so, it won't automatically update with new block updates etc. |
|
|
|
I read it twice to try understand all but still think I did not get it all like what private keys you mean? and from what you are saying I should go with the video and use only the wallet.dat file not the other 9,7gb files found in bitcoin map ?
Correct... the only part of the old data you really need is the wallet.dat file. This is the wallet data file that contains all the private keys you need to be able to access your bitcoins. and why do you think I cant start this wallet? cause I made a copy to the 1tb external HDD and what I remember it was an .exe file I saved but now I only find pieces or actually surprised at those 9,7 GB of data what is that about on first picture my wallet.dat is only 88kb big so whats using 9,7gb and is there a way of getting the real wallet somewhere saved on my HDD to click exe and it will open up with a password.
The 9.7gb's will be "blockchain data" that Bitcoin Core (likely called bitcoin-qt back when you created this) had downloaded. This blockchain data consists of the "raw" block files downloaded from other bitcoin nodes. It is not necessary to have kept this, as you can always just recover that from other bitcoin nodes... that's part of what nodes do, they share blockchain data And yes, an 88kb wallet.dat is not that unusual for an "old" wallet.dat from the earlier Bitcoin Core wallets. i don't understand why the wallet exe is not found.
Because it would appear you have backed up the old Bitcoin Core data directory... and not the actual application directory... On Windows, applications are generally installed to "C:\Program Files" (and/or "C:\Program Files (x86)")... this folder generally contains just the application itself (ie. the "exe" file)... and any support libraries etc. The "User Data" is generally stored in "AppData\Roaming\APPLICATIONNAME"... which for Bitcoin Core on Windows 10 will be "C:\Users\YOURUSERNAME\AppData\Roaming\Bitcoin" In any case, as mentioned above... the ONLY thing you need from the old backup, is the wallet.dat... that is the file that will contain all your private keys... and these private keys are what you need to be able to create/send bitcoin transactions. |
|
|
|
Hi etotheipi
etotheipi isn't responsible for Armory any more... it's all down to "goatpig" When I download armory wallet,it need to download all blockchain data.
It is so huge data,I can't download all these data.
How can I recover wallet without download blockchain data.
I want to move btc from armory wallet to a new hard wallet.
You don't need Bitcoin Core synced and/or the blockchain data downloaded... in fact, you don't even need Bitcoin Core installed to recover your coins You can simply do the following: 1. Download, install and run the latest Bitcoin Armory from here: https://btcarmory.com/2. In Bitcoin Armory, "recover your wallet":  Then select the appropriate recovery type (most likely the first one):  Then select which format your Armory backup is in:  3. After you have recovered your wallet from the paper wallet, you can follow my guide here to export your private keys: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg432556914. Once you have your private keys exported, you can use a wallet like Electrum to import the keys and send to your Hardware Wallet |
|
|
|
I saw that electrumG isn't avalible for linux. And I doesn't want to run a full node with BTG core wallet. Is there any other safe wallet for linux?
You should be able to run ElectrumG "from source" in Linux... (tested using Ubuntu 18.04) Download or clone the github repo: https://github.com/BTCGPU/electrumThen, in the "base" folder created from that (where "setup.py" is located): Install the dependencies: sudo python3 setup.py install
Compile the icons: pyrcc5 icons.qrc -o gui/qt/icons_rc.py
NOTE: if you get an error regarding pyrcc5 not being available... you'll probably need to run: sudo apt install pyqt5-dev-tools Start ElectrumG:  NOTE: I make no guarantees that this wallet is "safe"... it hasn't been updated in over 2 years!  |
|
|
|
|
Show Posts
