ok, so I installed bitcoin core latest version and it downloaded over 80G of chain block. Let's assume, just for the fun of it, there are 1000 bitcoin core users out there. That's ~8T of wasted disk space. and considering bitcoin will live another 7 years and it will grow of couse, that's like ~20T of disk space (1000 users remember?) for what? couldn't be a centerlaize, maybe mirrored, location that the client will ask for the chain block from there? Why do we need to download it?
The entire purpose of downloading the entire blockchain is to independently verify it and allow for the independent verification of every single block and transaction that occurs later. The only thing that a full node needs to "trust" is the genesis block, the very first block of the blockchain. This is actually hard coded into the software so that there is a defined starting point. After that, the node downloads all of the blocks from its peers. It will check each transaction in the block, and then check the block to ensure that it is valid. Because each block is chained together and transactions are also chained together, it is not possible to start from any point in the blockchain other than the beginning and still maintain trustlessness. |
|
|
|
On the latest dev, whenever I start the DB and then start Qt, as soon as Qt is up, the DB segfaults. This is the error: -INFO - 1470015657: (main.cpp:25) Ram usage level: 4
-INFO - 1470015657: (BlockUtils.cpp:1247) blkfile dir: /media/andy/Data/Programs/Bitcoin/data
-INFO - 1470015657: (BlockUtils.cpp:1248) lmdb dir: /media/andy/Data/Data/bitcoin/ArmoryData/databases
-INFO - 1470015657: (lmdb_wrapper.cpp:389) Opening databases...
-INFO - 1470015657: (BlockUtils.cpp:1438) Executing: doInitialSyncOnLoad
-INFO - 1470015657: (DatabaseBuilder.cpp:166) Reading headers from db
-WARN - 1470015657: (lmdb_wrapper.cpp:1203) No headers in DB yet!
-INFO - 1470015657: (DatabaseBuilder.cpp:199) Found 1 headers in db
-INFO - 1470015657: (DatabaseBuilder.cpp:49) updating HEADERS db
-DEBUG - 1470015657: (Blockchain.cpp:232) Organizing chain
-DEBUG - 1470015657: (Blockchain.cpp:232) Organizing chain
-INFO - 1470015657: (BitcoinP2P.cpp:725) Connected to Bitcoin node
0.001042s
-INFO - 1470015657: (BlockUtils.cpp:1549) Enabling zero-conf tracking
-INFO - 1470015756: (BDM_Server.cpp:573) registered bdv: f4f969be1fa8cf1e0807
-INFO - 1470015756: (BDM_supportClasses.cpp:387) Starting address registration process
-ERROR - 1470015756: (lmdb_wrapper.cpp:1462) Headers DB has no block at height: 0
-ERROR - 1470015756: (lmdb_wrapper.cpp:1442) No headers at height 0
Edit: GDB backtrace: #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
#1 0x000000000041f419 in BinaryData::copyFrom (this=0x7fffaf7fda80,
inData=0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff>, sz=80)
at BinaryData.h:195
#2 0x0000000000456092 in BlockHeader::unserialize (this=0x7fffaf7fda80,
ptr=0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff>, size=80)
at BlockObj.cpp:30
#3 0x0000000000456231 in BlockHeader::unserialize (this=0x7fffaf7fda80, str=...) at BlockObj.cpp:46
#4 0x00000000005aebf3 in BlockHeader::BlockHeader (this=0x7fffaf7fda80, str=...) at BlockObj.h:240
#5 0x00000000005a670b in BlockData::deserialize(unsigned char const*, unsigned long, BlockHeader const*, std::function<unsigned int ()>, bool) (this=0x7fffa8000d98,
data=0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff>,
size=4294967295, blockHeader=0x7fffe4001348, getID=..., checkMerkle=false)
at BlockDataMap.cpp:25
#6 0x0000000000571f5b in BlockchainScanner::<lambda(unsigned int)>::operator()(unsigned int) const
(__closure=0x7fffaf7fdd60, height=0) at BlockchainScanner.cpp:263
#7 0x0000000000572350 in BlockchainScanner::<lambda(std::function<void(const BlockData&)>)>::operator()(std::function<void(const BlockData&)>) const (__closure=0x7fffaf7fdd70, callback=...)
at BlockchainScanner.cpp:294
#8 0x000000000057321a in BlockchainScanner::scanBlockData (this=0x7fffd17f9a10, batch=...,
scrRefSet=...) at BlockchainScanner.cpp:450
#9 0x0000000000570920 in BlockchainScanner::<lambda(std::shared_ptr<BlockDataBatch>)>::operator()(std::shared_ptr<BlockDataBatch>) const (__closure=0x7fffb4000968, batch=...)
at BlockchainScanner.cpp:74
#10 0x0000000000581408 in std::_Bind_simple<BlockchainScanner::scan_nocheck(uint32_t)::<lambda(std::shared_ptr<BlockDataBatch>)>(std::shared_ptr<BlockDataBatch>)>::_M_invoke<0ul>(std::_Index_tuple<0ul>) (this=0x7fffb4000958) at /usr/include/c++/5/functional:1531
#11 0x000000000058109a in std::_Bind_simple<BlockchainScanner::scan_nocheck(uint32_t)::<lambda(std::shared_ptr<BlockDataBatch>)>(std::shared_ptr<BlockDataBatch>)>::operator()(void) (
this=0x7fffb4000958) at /usr/include/c++/5/functional:1520
#12 0x0000000000580e38 in std::thread::_Impl<std::_Bind_simple<BlockchainScanner::scan_nocheck(uint32_t)::<lambda(std::shared_ptr<BlockDataBatch>)>(std::shared_ptr<BlockDataBatch>)> >::_M_run(void) (
this=0x7fffb4000940) at /usr/include/c++/5/thread:115
#13 0x00007ffff78f2030 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#14 0x00007ffff7bc26aa in start_thread (arg=0x7fffaf7fe700) at pthread_create.c:333
#15 0x00007ffff705713d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
|
|
|
|
|
Yes. You check the source code. If you don't think the developer is trustworthy, check the source code and build it yourself from source.
|
|
|
|
|
Every machine you want to store Bitcoin on should have its own wallet. If you have the same wallet on two machines, there can and will be a lot of problems.
What I believe you are asking is why people have multiple addresses. Addresses are different from wallets. A wallet is a collection of addresses.
The reason for having multiple addresses is to preserve privacy and security. It is not advised to reuse addresses since it both allows people to see how much money you have and reduces plausible deniability. By giving out different addresses for different payments, the people paying you cannot know for certain how much money you have. For security, if ECDSA happens to be broken, not reusing addresses helps protect your Bitcoin. The public key for an address is exposed when you send Bitcoin. If ECDSA is broken. then by the time your public key is exposed (and thus allowing attackers to find the private key to steal your Bitcoin), the Bitcoin is already gone from the address so there is nothing to steal.
|
|
|
|
|
It appears that running just ArmoryQt.py without starting ArmoryDB beforehand just results in it never getting out of the "Preparing databases" stage.
|
|
|
|
Turns out I don't have coinbase tx to look at. I'll get me a few on the testnet and look at it directly (if you have a testnet address with a coinbase reward, feel free to provide it =P)
Just use regtest and mine your own regtest coins. You'll need 0.13 though in order to mine to a specific address. |
|
|
|
Getting build errors with ac2eb68: g++ -Icryptopp -Imdb -IBlockDataManager/fcgi -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7 -std=c++11 -O2 -pipe -fPIC -c SwigClient.cpp
g++ -Icryptopp -Imdb -IBlockDataManager/fcgi -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7 -std=c++11 -O2 -pipe -fPIC -c StringSockets.cpp
swig -c++ -python -threads -outdir ../ -v CppBlockUtils.i
Language subdirectory: python
Search paths:
./
./swig_lib/python/
/usr/share/swig2.0/python/
./swig_lib/
/usr/share/swig2.0/
Preprocessing...
Starting language-specific parse...
BtcUtils.h:277: Error: Syntax error in input(3).
Makefile:122: recipe for target 'CppBlockUtils_wrap.cxx' failed
make[1]: *** [CppBlockUtils_wrap.cxx] Error 1
make[1]: Leaving directory '/home/user/BitcoinArmory/cppForSwig'
Makefile:9: recipe for target 'all' failed
make: *** [all] Error 2
Debian 8.5 under Qubes 3. It might be something quick to fix, but I'd rather work with whatever the eventual goatpig solution is. Same error. |
|
|
|
Vanitygen simply does a brute force on random P2PKH addresses and checks them for your desired prefix. An implementation that brute forces random multisig P2SH addresses could accomplish the same task but it would be considerably slower. I think you could still use 2 of 3 (or any number really). Anybody want to take this on?  It would be possible, but you would end up having to brute force 3 keys instead of 1, which multiplies the possible search space by 6. Since it would also be a script, the script could also just have a nonce, and then you could also keep incrementing the nonce until the address is something you like. |
|
|
|
Does it mean that vanitygen can generate addresses starting with 3, i.e. multisig addresses (which would seemingly break the concept of such an address)? If it can't, there is only one way that it can have anything to do with such addresses...
That it just has nothing to do with them
You can generate a Wallet Address starting (seemingly) with any letter of the Alphabet or Numeral. http://cryptolife.net/upwg/ONLY "1's" and "3's" can be used with BitCoin Wallets (glossing over the test mode version of BitCoin for the moment). I've just rolled a Wallet Address 3fredGdggEbacP41PRkniuBwYV2DqSUkCv which has the right looking private key, so I might try installing it a little later on - If anyone wants to try sending it some dust, I won't object oclvanitygen64 -X 6 -D 0:0 -D 0:1 -o dump.txt 3fred
Difficulty: 4553521
Pattern: 3fred
Address: 3fredGdggEbacP41PRkniuBwYV2DqSUkCv The only way that you should be able to generate a vanity p2sh address would be to make 1 of 1 multsig addresses. T |
|
|
|
Let's isolate things a bit. Start from a fresh folder, spawn the db manually and build the testnet db. Then start the testnet client. Let's see if that works.
So I deleted the testnet folder. Then I started the Bitcoin Core testnet. Then I started ArmoryDB. Then I started ArmoryQt.py. It started without issue. Then I turned off the auto manage bitcoind and restarted Armory. I got the following error: (ERROR) Traceback (most recent call last):
File "ArmoryQt.py", line 6681, in method_signal
method()
File "ArmoryQt.py", line 6727, in completeBlockchainProcessingInitialization
self.setupLedgerViews()
File "ArmoryQt.py", line 6745, in setupLedgerViews
self.ledgerModel.setLedgerDelegate(TheBDM.bdv().getLedgerDelegateForWallets())
File "/home/andy/bitcoin/BitcoinArmory/CppBlockUtils.py", line 1248, in getLedgerDelegateForWallets
def getLedgerDelegateForWallets(self): return _CppBlockUtils.BlockDataViewer_getLedgerDelegateForWallets(self)
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7f1fd808c060> >
Traceback (most recent call last):
File "ArmoryQt.py", line 6681, in method_signal
method()
File "ArmoryQt.py", line 6727, in completeBlockchainProcessingInitialization
self.setupLedgerViews()
File "ArmoryQt.py", line 6745, in setupLedgerViews
self.ledgerModel.setLedgerDelegate(TheBDM.bdv().getLedgerDelegateForWallets())
File "/home/andy/bitcoin/BitcoinArmory/CppBlockUtils.py", line 1248, in getLedgerDelegateForWallets
def getLedgerDelegateForWallets(self): return _CppBlockUtils.BlockDataViewer_getLedgerDelegateForWallets(self)
<class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7f1fd808c060> >
There was also an error dialog saying that it could not find the headers folder in the data directory. Looking in the data directory, the databases folder was empty. So, I restarted both the DB and Qt and now there appears to be no error. |
|
|
|
Those trust you got are untrusted feedbacks. Feedbacks given by a DT are only the ones that will be shown and can be seen by anyone.
Sorry, can you please tell me what is a "DT" ?  DT is DefaultTrust. DefaultTrust is the trust list that each user gets by default. The list is composed of users that Theymos thinks are trustworthy (level 1) and then the users that those people think are trustworthy (level 2). You can remove DefaultTrust from your trust list and build your own trust list of users that you trust. However, changing your trust list will not change what other people see. The trust that someone sees is based on their trust list. |
|
|
|
|
Trust is only shown in the marketplace section (and maybe a few other places). It is not shown everywhere on the forum.
|
|
|
|
LOL you know its funny, I've looked at so many BTC addresses before,
and I don't think I ever realized they all started with "1"!
Not all of them start with 1. For example, CoinsBank Bitcoin addresses start with 3. As I got it, only addies generated with vanitygen start with 1 Bitcoin addresses either start with 1 or 3, doesn't matter who generates them. The addresses that start with 3 are p2sh addresses (aka multisig addresses). The addresses that start with 1 are normal one key addresses. There are produced by all wallets. |
|
|
|
Here is my dblog
Log file opened at 1469576952: /home/andy/.armory/regtest/dbLog.txt
-INFO - 1469576952: (main.cpp:30) Running on 8 threads
-INFO - 1469576952: (main.cpp:31) Ram usage level: 4
-INFO - 1469576952: (BlockUtils.cpp:1219) blkfile dir: /home/andy/.bitcoin/blocks
-INFO - 1469576952: (BlockUtils.cpp:1220) lmdb dir: /home/andy/.armory/regtest/databases
-INFO - 1469576952: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1469576952: (BlockUtils.cpp:1410) Executing: doInitialSyncOnLoad
-INFO - 1469576952: (DatabaseBuilder.cpp:166) Reading headers from db
-WARN - 1469576952: (lmdb_wrapper.cpp:1202) No headers in DB yet!
-INFO - 1469576952: (DatabaseBuilder.cpp:199) Found 1 headers in db
Log file opened at 1469576980: /home/andy/.armory/regtest/dbLog.txt
-INFO - 1469576980: (main.cpp:30) Running on 8 threads
-INFO - 1469576980: (main.cpp:31) Ram usage level: 4
-INFO - 1469576980: (BlockUtils.cpp:1219) blkfile dir: /home/andy/.bitcoin/blocks
-INFO - 1469576980: (BlockUtils.cpp:1220) lmdb dir: /home/andy/.armory/regtest/databases
-INFO - 1469576980: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1469576980: (BlockUtils.cpp:1410) Executing: doInitialSyncOnLoad
-INFO - 1469576980: (DatabaseBuilder.cpp:166) Reading headers from db
-WARN - 1469576980: (lmdb_wrapper.cpp:1202) No headers in DB yet!
-INFO - 1469576980: (DatabaseBuilder.cpp:199) Found 1 headers in db
-INFO - 1469576980: (DatabaseBuilder.cpp:49) updating HEADERS db
-DEBUG - 1469576980: (Blockchain.cpp:232) Organizing chain
-INFO - 1469576980: (DatabaseBuilder.cpp:53) updated HEADERS db in 0.00113s
-INFO - 1469576980: (BlockUtils.cpp:1521) Enabling zero-conf tracking
-INFO - 1469576980: (BitcoinP2P.cpp:691) Connected to Bitcoin node
Log file opened at 1469577029: /home/andy/.armory/regtest/dbLog.txt
-INFO - 1469577029: (main.cpp:30) Running on 8 threads
-INFO - 1469577029: (main.cpp:31) Ram usage level: 4
-INFO - 1469577029: (BlockUtils.cpp:1219) blkfile dir: /media/andy/Data/Programs/Bitcoin/data
-INFO - 1469577029: (BlockUtils.cpp:1220) lmdb dir: /home/andy/.armory/regtest/databases
-INFO - 1469577029: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1469577029: (BlockUtils.cpp:1410) Executing: doInitialSyncOnLoad
-INFO - 1469577029: (DatabaseBuilder.cpp:166) Reading headers from db
-WARN - 1469577029: (lmdb_wrapper.cpp:1202) No headers in DB yet!
-INFO - 1469577029: (DatabaseBuilder.cpp:199) Found 1 headers in db
-INFO - 1469577029: (DatabaseBuilder.cpp:49) updating HEADERS db
-DEBUG - 1469577029: (Blockchain.cpp:232) Organizing chain
-INFO - 1469577029: (DatabaseBuilder.cpp:53) updated HEADERS db in 0.000417s
-INFO - 1469577029: (BlockUtils.cpp:1521) Enabling zero-conf tracking
-INFO - 1469577034: (BDM_Server.cpp:571) registered bdv: 97bb4d41e3b42f629a93
-INFO - 1469577034: (BDM_supportClasses.cpp:387) Starting address registration process
-ERROR - 1469577034: (lmdb_wrapper.cpp:1461) Headers DB has no block at height: 0
-ERROR - 1469577034: (lmdb_wrapper.cpp:1441) No headers at height 0
Log file opened at 1469577043: /home/andy/.armory/regtest/dbLog.txt
-INFO - 1469577043: (main.cpp:30) Running on 8 threads
-INFO - 1469577043: (main.cpp:31) Ram usage level: 4
-INFO - 1469577043: (BlockUtils.cpp:1219) blkfile dir: /media/andy/Data/Programs/Bitcoin/data
-INFO - 1469577043: (BlockUtils.cpp:1220) lmdb dir: /home/andy/.armory/regtest/databases
-INFO - 1469577043: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1469577043: (BlockUtils.cpp:1410) Executing: doInitialSyncOnLoad
-INFO - 1469577043: (DatabaseBuilder.cpp:166) Reading headers from db
-WARN - 1469577043: (lmdb_wrapper.cpp:1202) No headers in DB yet!
-INFO - 1469577043: (DatabaseBuilder.cpp:199) Found 1 headers in db
-INFO - 1469577043: (DatabaseBuilder.cpp:49) updating HEADERS db
-DEBUG - -INFO - 14695770431469577043: : ((BitcoinP2P.cppBlockchain.cpp::691) Connected to Bitcoin node232
-INFO - 1469577043: (DatabaseBuilder.cpp:53) updated HEADERS db in 0.002176s
-INFO - 1469577043: (BlockUtils.cpp:1521) Enabling zero-conf tracking
-INFO - 1469577050: (BDM_Server.cpp:571) registered bdv: db2a604ec4cd038c1eeb
-INFO - 1469577050: (BDM_supportClasses.cpp:387) Starting address registration process
-ERROR - 1469577050: (lmdb_wrapper.cpp:1461) Headers DB has no block at height: 0
-ERROR - 1469577050: (lmdb_wrapper.cpp:1441) No headers at height 0
Log file opened at 1469577062: /home/andy/.armory/regtest/dbLog.txt
-INFO - 1469577062: (main.cpp:30) Running on 8 threads
-INFO - 1469577062: (main.cpp:31) Ram usage level: 4
-INFO - 1469577062: (BlockUtils.cpp:1219) blkfile dir: /media/andy/Data/Programs/Bitcoin/data/regtest/blocks
-INFO - 1469577062: (BlockUtils.cpp:1220) lmdb dir: /home/andy/.armory/regtest/databases
-INFO - 1469577062: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1469577062: (BlockUtils.cpp:1410) Executing: doInitialSyncOnLoad
-INFO - 1469577062: (DatabaseBuilder.cpp:166) Reading headers from db
-WARN - 1469577062: (lmdb_wrapper.cpp:1202) No headers in DB yet!
-INFO - 1469577062: (DatabaseBuilder.cpp:199) Found 1 headers in db
-INFO - 1469577062: (DatabaseBuilder.cpp:49) updating HEADERS db
-INFO - 1469577062: (BitcoinP2P.cpp:691) Connected to Bitcoin node
-INFO - 1469577062: (DatabaseBuilder.cpp:227) parsed block file #0
-DEBUG - 1469577062: (Blockchain.cpp:232) Organizing chain
-INFO - 1469577062: (DatabaseBuilder.cpp:53) updated HEADERS db in 0.04775s
-INFO - 1469577062: (BlockUtils.cpp:1521) Enabling zero-conf tracking
-INFO - 1469577065: (BDM_Server.cpp:571) registered bdv: 953a6d7b2058e212dbdd
-INFO - 1469577065: (BDM_supportClasses.cpp:387) Starting address registration process
-INFO - 1469577065: (BlockchainScanner.cpp:640) scanned from height #0 to #681
-INFO - 1469577065: (BlockchainScanner.cpp:222) scanned transaction history in 0.021318s
-INFO - 1469577065: (BlockchainScanner.cpp:640) scanned from height #681 to #681
-INFO - 1469577065: (BDM_supportClasses.cpp:498) Done with side scan of wallet
-INFO - 1469577070: (BDM_Server.cpp:602) unregistered bdv: 953a6d7b2058e212dbdd
-ERROR - 1469577070: (DataObject.h:223) exhausted entries in Arguments object
-INFO - 1469577077: (BDM_Server.cpp:571) registered bdv: d5afdcee13cacac3d529
-INFO - 1469577080: (BDM_Server.cpp:602) unregistered bdv: d5afdcee13cacac3d529
-ERROR - 1469577137: (DataObject.h:223) exhausted entries in Arguments object
-ERROR - 1469577137: (DataObject.h:223) exhausted entries in Arguments object
-ERROR - 1469577137: (DataObject.h:223) exhausted entries in Arguments object
-INFO - 1469581647: (BitcoinP2P.cpp:712) Disconnected from Bitcoin node
Log file opened at 1469721946: /home/andy/.armory/regtest/dbLog.txt
-INFO - 1469721946: (main.cpp:24) Running on 8 threads
-INFO - 1469721946: (main.cpp:25) Ram usage level: 4
-INFO - 1469721946: (BlockUtils.cpp:1219) blkfile dir: /media/andy/Data/Programs/Bitcoin/data/regtest/blocks
-INFO - 1469721946: (BlockUtils.cpp:1220) lmdb dir: /home/andy/.armory/regtest/databases
-INFO - 1469721946: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1469721946: (BlockUtils.cpp:1410) Executing: doInitialSyncOnLoad
-INFO - 1469721946: (DatabaseBuilder.cpp:166) Reading headers from db
-INFO - 1469721946: (BitcoinP2P.cpp:691) Connected to Bitcoin node
-INFO - 1469721946: (DatabaseBuilder.cpp:199) Found 682 headers in db
-INFO - 1469721946: (DatabaseBuilder.cpp:49) updating HEADERS db
-INFO - 1469721946: (DatabaseBuilder.cpp:227) parsed block file #0
-DEBUG - 1469721946: (Blockchain.cpp:232) Organizing chain
-INFO - 1469721946: (DatabaseBuilder.cpp:53) updated HEADERS db in 0.286681s
-INFO - 1469721946: (DatabaseBuilder.cpp:103) scanning new blocks from #682 to #682
-INFO - 1469721946: (BlockchainScanner.cpp:640) scanned from height #682 to #682
-INFO - 1469721946: (DatabaseBuilder.cpp:153) scanned new blocks in 0.01679s
-INFO - 1469721946: (DatabaseBuilder.cpp:157) init db in 0.309212s
-INFO - 1469721946: (BlockUtils.cpp:1521) Enabling zero-conf tracking
-INFO - 1469721947: (BDM_Server.cpp:571) registered bdv: 510cfc42b010fd290cae
-INFO - 1469721963: (BDM_Server.cpp:602) unregistered bdv: 510cfc42b010fd290cae
-INFO - 1469721963: (BDM_Server.cpp:515) proceeding to shutdown
-INFO - 1469721968: (BDM_Server.cpp:571) registered bdv: eafb083dbb49185f5236
-INFO - 1469722046: (BDM_supportClasses.cpp:387) Starting address registration process
-INFO - 1469722046: (BlockchainScanner.cpp:640) scanned from height #0 to #682
-INFO - 1469722046: (BlockchainScanner.cpp:222) scanned transaction history in 0.121126s
-INFO - 1469722046: (BlockchainScanner.cpp:640) scanned from height #682 to #682
-INFO - 1469722046: (BDM_supportClasses.cpp:498) Done with side scan of wallet rc7Qs5f4
-INFO - 1469722066: (BitcoinP2P.cpp:712) Disconnected from Bitcoin node
I was testing both dev and my segwit branch. The database dir was the default, which should have been empty. The satoshi datadir was custom.
Also, it looks like the build_installer.bat scripts are gone. |
|
|
|
HD support = Deterministic wallet? (I've never heard it called this before but I think youre talking about- "system of deriving keys from a single starting point known as a seed. The seed allows a user to easily back up and restore a wallet without needing any other information and can in some cases allow the creation of public addresses without the knowledge of the private key. " (From the wiki- https://en.bitcoin.it/wiki/Deterministic_wallet) HD means Heirarchical Deterministic, so a Deterministic Wallet. The commonly used specification for an HD wallet is BIP32. |
|
|
|
I'm getting a handful of these errors, followed by segfault: -ERROR - 1469735393: (StringSockets.cpp:384) FcgiSocket::writeAndRead exception: select error: 9 Getting as far as tx scanning stage, sometimes the segfault struck while the block parsing was still happening. Mine does the same, although there aren't many errors. It just says that a buffer overflow was detected and then segfaults. |
|
|
|
First of all thnx for sharing ur info, Signature Campaigns are not really good places for newbies to start. You should first learn the rules of the forum (read https://bitcointalk.org/index.php?topic=703657.0) by reading the stickied threads. Next, post, be active and contribute to discussions in order to rank up. Sig campaigns should not be the reason that you are here, but rather a reward for the posts that you make. The main purpose of being on this forum should be to discuss Bitcoin with others. If you do join a sig campaign, please, do not spam. Think before you post, if the post adds nothing new to the discussion, don't post. Secondly i have already read the rules , i don't usually post anything untill i read section's rules in any forum tht i join. i didn't mention that sig camping r the reason 4 me to join so don't attack me with tht , it was just a question as for the time i mentioned , i guess nobody likes his time 2 be wasted, and ofc am here to share wht ik and to increase my info and i don't think so i spammed anything. Idk but i feel like u r threatening me more than helping me .... Thnx Anyway .... Don't take it personally, it's reflexive. 99% of the time when a newbie comes to this forum and one of the first posts that they make is about joining a sig campaign, then usually the only reason that person joined is to join the sig campaign to get "free" Bitcoin. I advise that you not use shortened writing like that as it looks both juvenile and is hard to read. If you actually use the full words, post with correct punctuation and grammer, then you will be more respected and people are more likely to read what you write and consider whatever you are saying as it looks less spammy and is much easier to read. |
|
|
|
Hey guys,
I am new here so i need to know some basic terminologies , i know couple of them , but still in need to know more .
If u share with me what u know i would appreciate it.
1. What is Faucet ? sink faucet? lol
A Bitcoin Faucet is a service that gives away small amounts of Bitcoin. Typically the amounts are fixed and there is a wait time between claims by the same person. They do not pay out a lot and are not a good way of earning any Bitcoin but do allow for people to get started and experiment a little bit. 2. Signature camping is a good place to start? right? , but my question is , will i need to spend alot of time on this forum in order to make money from them?
Signature Campaigns are not really good places for newbies to start. You should first learn the rules of the forum (read https://bitcointalk.org/index.php?topic=703657.0) by reading the stickied threads. Next, post, be active and contribute to discussions in order to rank up. Sig campaigns should not be the reason that you are here, but rather a reward for the posts that you make. The main purpose of being on this forum should be to discuss Bitcoin with others. If you do join a sig campaign, please, do not spam. Think before you post, if the post adds nothing new to the discussion, don't post. 3. How trading works? is it like banks ? u deposit ur money there and then withdraw it with profit ? explain plz
No, that is not how trading works. Trading works by buying and selling Bitcoin (or any other currency or stocks). You deposit money and then buy and sell Bitcoin at different prices on an exchange in order to earn a profit. |
|
|
|
Thank you - all suggestions are appreciated and Ill pass everything onto my lawyer, any ideas are welcome for my defense.
Does anyone know how long walletexplorer.com has been active? and Im assuming that darknet links could be updated at anytime? For example lets say I took 100 coins into my wallet in March 2015. If I had done analyse on that day on walletexplorer.com, the address could of not been linked to a darknet site, then if I checked one year later it could then be linked to a darknet site as walletexplorer.com has updated the link. Is this a correct assumption?
Thank you
AFAIK, yes that is the correct assumption. The site isn't always up to date though. |
|
|
|
Thank for the answer.
Note that making a backup once is NOT enough! By default it contains 100 private keys, once you've used them all it creates new keys, which means you need to make a new backup!
It seems my understanding was faulty. I though it's like for ssh, you have one key and it's used all the time. But now I see that I was wrong. When do the private keys are being used? is it a key for every transaction? The keys are used for every new address that is made. This is when you get a new receiving address for every time you want someone sends you Bitcoin (you should not reuse addresses). A new address will usually be used when you send as well since there is usually a change address. So you will need to backup every 100 transactions, both receive and send. |
|
|
|
|
Show Posts
