 Show Posts
|
|
Pages: [1] 2 3 4 »
|
|
like any p2p networks, a list of initial seed nodes are either preconfigured or harded coded so that the startup and bootstraping can work without knowing all the nodes out there.
|
|
|
|
|
yes impose a collateral on tBTC implies they have certain values while they should not...
|
|
|
|
|
Physical tokens/coins defies the very point of bitcoin's decentralized idiom, since it is physical, it is searchable and confeitable by the authorities which you don't want to risk with.
|
|
|
|
|
Hi BYTOM offcial, i have some ERC20 BTM tokens, can you help how can I swap those to the real mainnet BTM tokens?
|
|
|
|
Accod. to the guide, I have to deposit the ERC20 to one of the exchanges, and the exchange will do the swap, but those mentioned exchanges have stopped support this swap. I wonder why isn't there a non-exchange swap... |
|
|
|
|
I just found out there are some BTM in my ether wallet, but looks like bytom has lunched their own network for some time, is there anyway to swap those to the real BTM token? Thanks
|
|
|
|
|
李笑来声明从此退出出区块链投资，那之前进他的收费群的会员费退了没有，谁知道？
|
|
|
|
helping her out like reselling products she needed in exchange for her Bitcoins
I would not call that living solely on bitcoins, nearly none of the merchants accept bitcoins there. If she gets a crypto backed card with visa membership it would be a lot easier to live a normal life. |
|
|
|
Hi to all,
I'm so confused about that, is the mentioned stages in this post correct to do right now for creating a new Alt Coin?
Thanks
Yes, it is in a sense, but unless you want something POW coins similar to bitcoin, today most coins are created as ERC20 on Ethereum network. How Can I do that? Just follow the guide  What specifically do you want to do? |
|
|
|
Hi to all,
I'm so confused about that, is the mentioned stages in this post correct to do right now for creating a new Alt Coin?
Thanks
Yes, it is in a sense, but unless you want something POW coins similar to bitcoin, today most coins are created as ERC20 on Ethereum network. |
|
|
|
Oh, sorry I forgot to mention, in order to mine, the node has to connect to at least one peer node. So you need to run another instance of bitcoind and let it connect to the first node, like:
what is the reason the node has to connect to at least one peer node, in order for miner to run? Mined blocks needs to be broadcast and confirmed by the network, with only one node your blocks cannot be confirmed. Also this check is hard wired in bitcoin's source code, so it's a must-met condition. |
|
|
|
Thanks a lot.
I have set up and began mining, but have not mined Block 1 several hours.
Should I modify the difficulty of POW ? and how to ?
Thanks in advance.
The debug.log saying, ...... 2018-05-26 23:46:14 ERROR: ProcessNewBlock: AcceptBlock FAILED 2018-05-26 23:46:14 ERROR: ProcessNewBlock: AcceptBlock FAILED 2018-05-26 23:46:14 ERROR: ProcessNewBlock: AcceptBlock FAILED 2018-05-26 23:46:14 ERROR: ProcessNewBlock: AcceptBlock FAILED 2018-05-26 23:46:14 ERROR: ProcessNewBlock: AcceptBlock FAILED 2018-05-26 23:46:14 ERROR: ProcessNewBlock: AcceptBlock FAILED ...... Is there something wrong? Hi, what's your command line to run bitcoind and the miner? |
|
|
|
So bitcoin's API, commands, daemon feature is same at all other alt-coins?
And eth ERC20 token does not have any source github, API, commands, daemon, right?
No, each coins have their own features and APIs, you have to refer to that specific coin's documentation to find out. ERC20 is a protocol running on top of Ethereum network, you can find links to github and docs here https://ethereum.org/. |
|
|
|
|
As the documentation suggests, if double encryption is enabled, there are two passwords, the first one is the rpcpassword you pass in when calling the rpc, pass it as the command line argument to "-rpcpassword", and the second password is your set with "walletpassphrase" api call. That means before calling any api that requires second password, call "walletpassphrase <password> <timeout in seconds>" to unlock the wallet.
|
|
|
|
Thank you for your reply.
I do generate my own genesis block. It seems that it is just keeping downloading.
It would be a lot helpful if you could run a git diff on your workspace and paste the change you have made, so that we can identify the problem. Thank you very much for your reply. Those are the changes I made: https://github.com/zhq422194011/bitcoin/commit/e0b0d5c9b4be209cf640cf6e8ae29bf1525c58daMy bitcoin.conf is: server=1
gen=1
rpcbind=0.0.0.0
rpcuser=rpcuser
rpcpassword=111111
rpcallowip=127.0.0.1
rpcallowip=0.0.0.0/0
listen=1
I run the following two bitcoinds: sudo ~/bitcoin/src/bitcoind -addnode=127.0.0.1:9332 -port=8963 -rpcport=8962 -debug=rpc -dns=0 -dnsseed=0
sudo ~/bitcoin/src/bitcoind -datadir=$HOME/.bitcoin2 -addnode=127.0.0.1:8962 -port=9333 -rpcport=9332 -debug=rpc -dns=0 -dnsseed=0
When I run ./bitcoin-cli getblocktemplate, I got: error code: -10
error message:
Bitcoin is downloading blocks...
The code change looks right, for the first node, don't use -addnode, becuase the second node hasn't started yet, also add "-connect=0 -listen=1 -maxtipage=$((24*60*60*5000))" to it, for second node, use addnode to add the first node. |
|
|
|
Thank you for your reply.
I do generate my own genesis block. It seems that it is just keeping downloading.
It would be a lot helpful if you could run a git diff on your workspace and paste the change you have made, so that we can identify the problem. |
|
|
|
Thank you very much for your reply.
One more question is that I do not know why it is keeping "Bitcoin is downloading blocks..."
Because of this, the getblocktemplate will not work.
Did you generate your own genesis block? If not, try follow step 13, set max tip age to a very large period of time. |
|
|
|
If there is one coin daemon running, and at that same server, users will join, then issueing addresses to each users.
Then if I want the users can send & receive to/from his address, when I issue address to user, should I attach account string value to that issues address?
Account in bitcoin daemon is more like a lable string, address is enough to send and receive coins. But if you want to set a new account for each user for management purpose, you can do that using bitcoind's rpc, refer to getaccountaddress api. getaccountaddress
Returns the current bitcoin address for receiving payments to this account. If <account> does not exist, it will be created along with an associated new address that will be returned.
|
|
|
|
|
