Ahh, you mean the magic bytes which identify the network it uses. The easiest way to see what the magic bytes are is to just connect to the node. The first 4 bytes that they send are the magic bytes. The messages of every altcoin based on Bitcoin are basically the same format, so it should be fairly trivial to get the magic bytes as they are the first four bytes of every message. |
|
|
|
|
What do you mean by "pchMessageBytes"? I can't find that anywhere (grepped the entire source).
There is nothing in the protocol that makes a node deliberately disconnect from and refuse to connect to a node that uses an old version number. Nodes will instead just not send the new message types.
Also, there are no unique bytes that must be kept secret in any of the messages.
|
|
|
|
This method should work and anytime you can use private key to install in other wallet like electrum or block chain.. am i right sir?
It works to extract the private key of an address from Bitcoin Core and all of its derivatives. This private key is in Wallet Import Format so it can be imported into any wallet that supports WIF (basically every wallet out there). |
|
|
|
Also, it IS possible to "redirect this bitcoin to another wallet or to a site where you wish to spend it".
You can extract the private key of the bitcoin address that you sent the bitcoins to, and you can then import that private key into any SPV wallet or website account that allows importing of private keys. That will give you immediate access to the bitcoins so you can spend them.
Lovely! Thank you so much for that information. If I could ask, how would I extract the private key? Again, thank you for providing such good incite. You have to open the Debug Console and use where <address> is the address you want the private key of. If your wallet is locked, you will need to do walletpassphrase <passphrase> 120 where <passphrase> is your passphrase. This will unlock your wallet for 120 seconds so that you can do dumpprivkey for all of the addresses that you need. |
|
|
|
Is there an issue if still using 0.12 core version.
No, there are no known problems with 0.12.1, and both the most recent major version and the previous major version are officially supported. So 0.12 will be supported until 0.14 comes out. I recommend waiting a few months to upgrade on sensitive systems just in case any bugs are found. Will a future version prevent an older version from connecting at some later point in time? Probably not, but an older version will definitely not be able to connect to a future version at some point in time. I have a PortableApps BitCoin Wallet that I try to play catch up with the block chain, but that Wallet version for PA hasn't been updated in quite a while. (and unless the NBN comes to my area soon (and is affordable as well) I won't be able to have a local copy of the block chain anytime soon...)
It depends on the version of that wallet. I know for a fact that really old versions of Bitcoin are incompatible with the current network. |
|
|
|
Okay...
i had an issue with the walletpassphase. no matter what i did, i kept getting an error. so i thought maybe it doesn't like the spaces in my current passphrase, so that gave me pause to think that if it didn't like it in the concole, would i even be able to change the passphrase as it needed to be entered to change it. i changed it with no worries. then went back to the console and it worked, so perhaps it was that it did not like the spaces.
No, the console will not like spaces. Each parameter is space separated, so it will think whatever you type is is multiple parameters. Rather what you should have done is put quotes (") around your password. That should have fixed the problem. quick update.
this appears to have worked.
the initial transaction now has an 'x' (which when hovered over with the cursor says conflicted) in the 'transaction status' box instead of the'?' that previously existed. now there is a new transaction with a 'clock' in the 'transaction status' box with it already having 1 confirmation.
Yes. That X means that transaction is conflicted (by your second one). The thing is, it will remain there, so if you want it gone, you will need to use -zapwallettxs |
|
|
|
|
Don't promote them here. It is against the rules.
|
|
|
|
This is strange. If I use the shortcut I made to launch Armory, it doesn't work. This is the error from the log: 2016-09-03 01:02 (INFO) -- ArmoryUtils.py:639 - Executing popen: ['./ArmoryDB', '--db-type="DB_FULL"', '--spawnId="5uWPvi3P2wvYyo2xNdpeWKU4spxWvHuDRuCJ9gfxevYd"', '--satoshi-datadir="/media/andy/Data/Programs/Bitcoin/data/blocks"', '--dbdir="/media/andy/Data/Data/bitcoin/ArmoryData/databases"']
2016-09-03 01:02 (ERROR) -- Traceback (most recent call last):
File "/home/andy/bitcoin/BitcoinArmory/ArmoryQt.py", line 6631, in method_signal
method()
File "/home/andy/bitcoin/BitcoinArmory/ArmoryQt.py", line 6668, in completeBlockchainProcessingInitialization
gotDB = self.startArmoryDBIfNecessary()
File "/home/andy/bitcoin/BitcoinArmory/ArmoryQt.py", line 2198, in startArmoryDBIfNecessary
spawnId = TheSDM.spawnDB(TheBDM.armoryDBDir)
File "/home/andy/bitcoin/BitcoinArmory/SDM.py", line 490, in spawnDB
launchProcess(pargs, **kargs)
File "/home/andy/bitcoin/BitcoinArmory/armoryengine/ArmoryUtils.py", line 642, in launchProcess
return Popen(cmd, stdin=PIPE, stdout=PIPE, stderr=PIPE, *args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
However if I run the same command from the terminal, I have no problems whatsoever. I am running Ubuntu 16.04. This is probably an issue with my system, but I think it is something to note. Armory is trying to open ArmoryDB as a relative path. That only works if you are have used cd to enter the Armory source tree first. The solution is for Armory to use absolute paths, so people don't need to be in the same directory as Armory to run it. So this update breaks shortcuts right now. That is a bit of an issue. |
|
|
|
Fast routing? I don't think you understand how addresses work.
Imagine if we have addresses like email: user@domain. It's not a problem for one host to have full list of "domains" and all list of routes. So, you will be able to find route from one domain to other, that will be extremely fast. You don't need addresses like email addresses for that. You just need to have some sort of central authority that has a list of all open channels that would make it easier to route payments. The whole email addresses with domains just doesn't really make sense to me as to how that would be any better than normal addresses. If you use something else, you will get slow network, like TOR or BitMessage. I want extremely fast payment system, like a chat, not like BitMessage. That's all I want to say.  Neither of those things are comparable. All of those systems (tor, bitmessage, and ln) use completely different protocols, you cannot compare them. |
|
|
|
I am confused here when you are saying bitcoin to your electrum wallet. I thought that electrum can only be stored in these sort of wallets.  Electrum is not a coin. It is the name of a bitcoin wallet. See https://electrum.orgYou're probably thinking of Ethereum.
OP. I suggest that you install Electrum onto another computer and restore your wallet on that computer. Then make a new Electrum wallet and send all of your Bitcoin to the new Electrum wallet. This way if anyone were to try to hack your wallet, they would not be able to get any of your Bitcoin. You can also remove the hard drive and open it up in another computer and then remove the wallet files. |
|
|
|
|
You can only upload images after you become a Jr. Member. Please use the search function to find answers to your questions. This question has been asked hundreds of times already.
|
|
|
|
Putting it in a file as suggested will work. But in looking online, it seems to me that Ctrl-D should signal end-of-file on OSX. I don't know why it's not working. I've never used a Mac, though. Can anyone who does use OSX share their experience?
It might be Cmd+D (command, the stupid apple thing that basically replaces ctrl). |
|
|
|
OK, I have a question. Say: I enabled prune mode and Bitcoin Core effectively started working in this mode.
But it is one way ticket if I ever want to go back to 'full' mode I need to download and verify whole blockchain once again there is no shortcuts?
Yes, you will have to redownload the entire blockchain, there are no shortcuts Also minimal number from that command line to start prune mode: "550" - is it linked directly to disk space pruned blockchain will take?
That number is the number of Megabytes to allocate for block and undo files. Each block can have up to 1 Mb of block file and 1 Mb of undo file. 550 will thus store, at a minimum, ~2 days of blocks. |
|
|
|
Ok I tried saved the below text to a txt file: -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
f94123e37530f9de25988ff93e5568a93aa5146f689e63fb0ec1f962cf0bbfcd bitcoin-0.13.0-aarch64-linux-gnu.tar.gz
7c657ec6f6a5dbb93b9394da510d5dff8dd461df8b80a9410f994bc53c876303 bitcoin-0.13.0-arm-linux-gnueabihf.tar.gz
d6da2801dd9d92183beea16d0f57edcea85fc749cdc2abec543096c8635ad244 bitcoin-0.13.0-i686-pc-linux-gnu.tar.gz
2f67ac67b935368e06f2f3b83f0173be641eef799e45d0a267efc0b9802ca8d2 bitcoin-0.13.0-osx64.tar.gz
e7fed095f1fb833d167697c19527d735e43ab2688564887b80b76c3c349f85b0 bitcoin-0.13.0-osx.dmg
0c7d7049689bb17f4256f1e5ec20777f42acef61814d434b38e6c17091161cda bitcoin-0.13.0.tar.gz
213e6626ad1f7a0c7a0ae2216edd9c8f7b9617c84287c17c15290feca0b8f13b bitcoin-0.13.0-win32-setup.exe
5c5bd6d31e4f764e33f2f3034e97e34789c3066a62319ae8d6a6011251187f7c bitcoin-0.13.0-win32.zip
c94f351fd5266e07d2132d45dd831d87d0e7fdb673d5a0ba48638e2f9f8339fc bitcoin-0.13.0-win64-setup.exe
54606c9a4fd32b826ceab4da9335d7a34a380859fa9495bf35a9e9c0dd9b6298 bitcoin-0.13.0-win64.2d61f88621301bbb00512376287f9df4568255f8b98bc10547dced96c8 bitcoin-0.13.0-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJXvFxeAAoJEJDIAZ42wulkCswP/19dAX2bLAMWBVAfjQSyJDzp
KvqR/9zsMI6HO1wMrSvEmL4dP6bePvd6ZgZ2UO7qCT337s6LE80FWdU6ZQnmczK2
xFy2VXl8ewCrDSexuCfEnnjbuTyoVBbfqoxBag7UZ6atuXV5pwYvThknRDldycah
PJXHN59cyhnpU7hQoblq0Gqk8FK4G05KsIdJrllaXKNTb1xDou/JpXDaqP6kHu75
kfMGAMWvynLZkR9lZZ2hdLItWxY0s2BOb3Uyi0clxjk8XMI1x8GSIgyS4ANX8xOl
9oToxykI21STJlwFBqJlx9FXrdG8YHndO5zhQEfshnoTzAsPReRV2mzmW3iS1vrF
EV1VHUY04jab6TFJ/7xzywmPF4mYsL6GXDcHxB0c58wFU1pybPC/46CPFxIwOsdY
rCuDtcVYtWswIYAn4mtA3DkWFeNEMUi5HKSdxm3smXKEOViWoipesXaQSJGHeNyK
xo4NpqaZr4aDqlZSZftdipyenOtSqSEeN3HCkJRTiMPzIZcbMoVrw/AFMcUEj6iO
gck1tbqGzI8IuvsArorm9q8TydoM1lcQo9FNeGSHKCs5EWOekDljRWRUGLMk717S
9SQwcOe3mXxwDX84m8ftbqozCw3dAW6OLF2QmswEdM4rKY1mrsIy6v6zoFkjPowK
B33vu2QZLMG5wazPw+Kz
=1/IW
-----END PGP SIGNATURE----- And this is what came up: gpg --verify test.txt
gpg: Signature made Tue 23 Aug 15:23:26 2016 BST using RSA key ID 36C2E964
gpg: BAD signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <laanwj@gmail.com>" [unknown] That's because your file is wrong. This line is incorrect: 54606c9a4fd32b826ceab4da9335d7a34a380859fa9495bf35a9e9c0dd9b6298 bitcoin-0.13.0-win64.2d61f88621301bbb00512376287f9df4568255f8b98bc10547dced96c8 bitcoin-0.13.0-x86_64-linux-gnu.tar.gz It should really be these two lines: 54606c9a4fd32b826ceab4da9335d7a34a380859fa9495bf35a9e9c0dd9b6298 bitcoin-0.13.0-win64.zip
bcc1e42d61f88621301bbb00512376287f9df4568255f8b98bc10547dced96c8 bitcoin-0.13.0-x86_64-linux-gnu.tar.gz
However how do I actually check the .dmg file that contains the installer is the right one? If I run: gpg --verify bitcoin-0.13.0-osx.dmg I get: gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line. That's because the files themselves are not pgp signed and do not have any signatures. Because it expects a signature file. And if I use the file that has the signatures that you can download from https://bitcoin.org/bin/bitcoin-core-0.13.0/SHA256SUMS.asc, I get: gpg --verify SHA256SUMS.asc
gpg: Signature made Tue 23 Aug 15:23:26 2016 BST using RSA key ID 36C2E964
gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <laanwj@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964
gpg: There is no indication that the signature belongs to the owner.Doesn't inspire 100% confidence... Maybe that's how it's supposed to come up? Indeed it is. PGP does not have a centralized trust server. You are supposed to build your own web of trust by trusting other people's keys and setting a trust depth (kinda like the trust system here, minus DT). Since you have not trusted the release key, GPG will warn you that the key is untrusted. So I did run the below first as suggestend in the OP: shasum -a 256 bitcoin-0.13.0-osx.dmg And got the right shasum. If I have that right together with the last output above from checking the signatures, is that all I need to trust the .dmg file is genuine? Thanks for the help in advance, this is good learning, and thanks to theymos for the heads up note on top of this forum! Yes that is all you need to trust that the .dmg is the right file. |
|
|
|
Hello,
Blockchain.info is now using BIP44 wallet which I need to understand principle in terms of back ups in order to trust this kind of wallet.
According to what is said, a simple 12 words passphrase can unable the full recovery of the wallet. This is true for blockchain.info and other platforms supporting BIP 44.
But there must be a link between all those platforms supporting BIP 44 allowing wallet recovery on one platform with a passphrase generated on an other platform? what is this link?
thanks,
BIP 44 is a specification (it is actually an extension of BIP 32). In order for something to use BIP 44, it must follow the detailed spec that Arkazie posted above. This spec defines a specific algorithm that must be used when deriving addresses. A master private key (encoded as the seed), it will always return the same addresses if the specified algorithm is followed. This is regardless of the wallet so long as it implements BIP 44 correctly. |
|
|
|
I sent a transaction an hour ago through Bitcoin Core using the default fee, and it's still unconfirmed. Is something going on with the network? I have never had problems with Bitcoin Core when sending a transaction using the recommended fee, but this time its taking too long. It's already past 1 hour actually.
Well the default recommended fee is for it to confirm within 25 blocks, so don't be too surprised that it is slow. If you want fast confirmations, you have to move the slider all the way to the right to "fast". |
|
|
|
This is strange. If I use the shortcut I made to launch Armory, it doesn't work. This is the error from the log: 2016-09-03 01:02 (INFO) -- ArmoryUtils.py:639 - Executing popen: ['./ArmoryDB', '--db-type="DB_FULL"', '--spawnId="5uWPvi3P2wvYyo2xNdpeWKU4spxWvHuDRuCJ9gfxevYd"', '--satoshi-datadir="/media/andy/Data/Programs/Bitcoin/data/blocks"', '--dbdir="/media/andy/Data/Data/bitcoin/ArmoryData/databases"']
2016-09-03 01:02 (ERROR) -- Traceback (most recent call last):
File "/home/andy/bitcoin/BitcoinArmory/ArmoryQt.py", line 6631, in method_signal
method()
File "/home/andy/bitcoin/BitcoinArmory/ArmoryQt.py", line 6668, in completeBlockchainProcessingInitialization
gotDB = self.startArmoryDBIfNecessary()
File "/home/andy/bitcoin/BitcoinArmory/ArmoryQt.py", line 2198, in startArmoryDBIfNecessary
spawnId = TheSDM.spawnDB(TheBDM.armoryDBDir)
File "/home/andy/bitcoin/BitcoinArmory/SDM.py", line 490, in spawnDB
launchProcess(pargs, **kargs)
File "/home/andy/bitcoin/BitcoinArmory/armoryengine/ArmoryUtils.py", line 642, in launchProcess
return Popen(cmd, stdin=PIPE, stdout=PIPE, stderr=PIPE, *args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
However if I run the same command from the terminal, I have no problems whatsoever. I am running Ubuntu 16.04. This is probably an issue with my system, but I think it is something to note. |
|
|
|
Yes, LN should use the same addresses for commitment transactions, that's true. But LN may also use anything else, for example "email-like" addresses username@example.com. Such addresses could be very usefull for fast routing. Fast routing? I don't think you understand how addresses work. |
|
|
|
You earn bitcoin like you do any other money, you must work for it. You can: - Sell some sort of good in exchange for bitcoin
- Offer some sort of service in exchange for bitcoin
- Beg for bitcoin and hope that people give you some out of the charity of their hearts (against forum rules)
Scam, back, steal, or otherwise obtain Button that is not yours (illegal)
|
|
|
|
|
LN does not specify special addresses because there is no need for ten. It uses normal p2sh addresses and the transactions are normal bitcoin transactions. It utilizes what already exists, it doesn't make anything new.
|
|
|
|
|
Show Posts
