I tried to compile newest version of coin core at AWS's t2 micro EC2 instance, it fails with this erros.
--------- /usr/bin/ar: `u' modifier ignored since `D' is the default (see `U') CXX gamecoind-bitcoind.o CXX libbitcoin_server_a-addrdb.o CXX libbitcoin_server_a-addrman.o CXX libbitcoin_server_a-bloom.o CXX libbitcoin_server_a-blockencodings.o CXX libbitcoin_server_a-chain.o CXX libbitcoin_server_a-checkpoints.o CXX consensus/libbitcoin_server_a-tx_verify.o CXX libbitcoin_server_a-httprpc.o CXX libbitcoin_server_a-httpserver.o CXX libbitcoin_server_a-init.o virtual memory exhausted: Cannot allocate memory Makefile:5658: recipe for target 'libbitcoin_server_a-init.o' failed make[2]: *** [libbitcoin_server_a-init.o] Error 1
-------------
t2 micro spec is 1 cpu, 1g ram.
So ram shortage is reason of this error?
Then how much ram should be to compile?
4g? or 8g?
And how many cpu needed and how much ssh (or hdd) space needed?
Thanks.
|
|
|
Sorry for bother. Some crazy guy destroyed discord... So I made again. https://discord.gg/vtTve2vPlease share this and restore whole things before.
|
|
|
Someone propose that I make getnewaddress and dumpprivkey that address,
he will do same at his wallet, and we exchange each other's privkey generated from above, then importprivkey.
and if I input coin to there, that become multisig, both signing need and safe.
Is this true?
No scam factor here?
|
|
|
After I pre-mined whole max money at once, still I can earn mining reward when I mining.
And my immature balance shows over max_money variable I set at source code.
Then if I get and spend more than max money, what happen?
Is this normal, no problem?
|
|
|
Originally, I didn't send unconfirmed balance. I sent from my balance.
You did. Your 'balance' does also show unconfirmed balance. If you do have one 1 BTC output and create a transaction 'sending 0.1 btc', your transaction will basically look like this: Input:1 BTC -> Output1: 0.1 BTC, Output2:0.9 BTCAfter you broadcast this transactions your balance shows 0.9 btc. But this is an unconfirmed balance. And since you were repeating this step 80 times.. it definitely makes sense that the chain of unconfirmed transactions got too long to be accepted by the majority of nodes. -> This make senses... And how to rebroadcast it?
Look here. Then how about other alt coin's case? How to rebroadcast it? Its same inherited from bitcoin source.
|
|
|
If your transactions are spending unconfirmed transactions, then at some point the chain of unconfirmed transactions will be too long and the transactions won't be accepted by your own node's mempool or other nodes' mempools. This is probably happening resulting in your transactions becoming "stuck" as the other mining node rejects the transactions. You will need to rebroadcast them to that node, and not do them all at once.
Originally, I didn't send unconfirmed balance. I sent from my balance. And how to rebroadcast it? And it almost took 1~2 days to confirm, strange thing is, when I sent 50 mil, or 80 mil, it stucked, but when I sent 10 mil, it goes smoothly and fastly.
|
|
|
I processed 100 around transactions at once via daemon console, by sendtoaddress command to same address.
I repeatedly typed keyboard fastly with up arrow key and enter key.
From A wallet that has 90 billion coin to B wallet.
50 million at one time sendtoaddress.
After did like 70~80 times, suddenly it says balance is 20, it should be 80 billion.
79 billion is at unconfirmed balance.
Why this happen? Other computer mining this coin, but it can't deal all those 70~80 transactions at one time, but 1~2 transactions at one block.
I see this phenomenon at first time, how describe this situation?
|
|
|
I only know %s followed after walletnotify, and this is transaction ID's option,
are there other option like %x or %a or whatever different to receive different variables?
Thanks.
|
|
|
Thanks! So Electrum is not the choice if I installed bitcoin core for some web service?
|
|
|
The procedure to go would most likely look like this: 1. Create an address on the cold storage system 2. Bring this address into the second wallet, which is connected to the internet (the hot wallet, or the live system). As mentioned by Heisenberg_Hunter, make this a watch only address in the hot wallet. Then you can see at all times the balance on this address. 3. On the hot wallet you can now create a transaction, and save it as raw transaction on a USB stick or similar. 4. Bring the USB stick to your cold storage system, load the transaction into the wallet, and sign it. 5. After signature, store it again on USB stick, and bring it to the hot wallet system 6. send the transaction.
The procedures how to load addresses or save/export transactions vary from wallet to wallet.
Thanks, but I totally don't understand what this means and how to do this actually, I never heard about this. So this is so-called [multi-sig] wallet? or? How to perform this procedure actually? 2. Bring this address into the second wallet, -> How? Commands? 3. -> How? This is not [sendtoaddress]? 4. load the transaction into the wallet, and sign it. -> How? I don't know at all. 5. bring it to the hot wallet system -> How? 6. ?? finally [sendtoaddress]? And how about coins that does not have this features?
|
|
|
Yes, just send the coins to a wallet whitout a password. But why would you leave your wallet unprotected? If you have an larger amount of coins/token value I would in any case consider buying a hardware wallet like Ledger Nano S!
Then how deal the case that daemon communicate with web? Need to make address, send coin. Then incoming code should have unlock password process?
|
|
|
Is there a reason for you to create another thread asking the same question? You can simply google the answer yourself. And you should really start googling. You are asking VERY basic questions all the time (even tho they already have been answered!). One helpful answer has been given in your older thread: https://bitcointalk.org/index.php?topic=4469028.msg40079188I wonder why you actually created this thread if you already know everything you should about this command, especially since you already have asked about it in your previous thread.. Because I found that sometimes multiple same confirmations tx ids come into notification files that generated when custom php file being called. And sometimes that tx id comes when its confirmations become over 100 or 300, so later time from confs 0 or 1.
|
|
|
As title, How to make coin's wallet address sanity check algorithm?
To block user's trial of send coin to wrong address or other coin's address.
|
|
|
I know there is command that can change password , but are there also remove password and make wallet status as no password?
|
|
|
At .conf file's walletnotify option, I tested this with actual coin deposit to my daemon, and custom php script,
So coin daemon called this walletnotify only 3 times right?
1. When receive coin (confirmation = 0)
2. When 1's tx's confirmation become 1
3. When send coin
Is this right? or coin daemon calling more than these cases? What cases ?
|
|
|
I forget coin's window wallet program's password.
So I can't send coin.
Then this coin is lost forever?
Are there no restore method?
Just default qt wallet program.
|
|
|
I found that when try to send big number like 300,000 coin at once, then daemon become slow, then error says transaction size limit is over.
So I think this because, wallet try to gather many address's balance to make total 300,000, so when it become exceed size, then it errors, right?
So how can I increase this size at sourcecode?
|
|
|
If I install coin at ubuntu root directroy, then it uses main ssd drive,
this is too pricy at amazon.web server, so how can I change directory to which download block datas?
I want to use more cheap and large size HDD drive for download large block datas.
|
|
|
wallet.dat file is important,
1. so is it enough to backup it just once?
2. or should it be backup continuously?
I think 1 is right. Is this right?
|
|
|
|