Topic: Some questions about bitcoind daemon (Read 1821 times)

You can also only allow transactions if at least 0.0005 (or even up to 0.01) BTC is present in the user's account, but only subtract the actually used fee?

great advice.

thank you again.

so i will have to pre charge 0.01btc for every out going bitcoin translations.

If you're going to run a service which needs to be able to send transactions by itself, my only advice it so only run it on hardware you own, or pay the hosting company for the level of protection you need. At least, for now. When multisig transaction become commonplace, other solutions may be possible.

If you're just going to receive transactions, pre-generate 1000 addresses and put them on the webserver, but run no live bitcoind there.


That's currently hard: you can set the voluntary fee to 0, but bitcoind will always add a fee if it considers it absolutely necessary (too small outputs, too young/small inputs, too large, ...). This is usually very small, but whether it is necessary can depend on random factors (the input coin selection is random, so the fee requirement may or may not be there, though it rarely has much influence.

very helpful, any ideas for others 2 questions?

walletpassphrase is still write in source code, if vps got hacked, hacker still can read this password.

thank you so much

You can access the wallet encryption via the walletpassphrase, walletlock, encryptwallet and walletpassphrasechange commands. The RPC password however is something completely different: it's only for authenticating the RPC call itself. Wallet encryption is independent.

thanks for your reply.

i don't mind its free or not, but i need to know and charge the fee before client actually send his bitcoins out, so his account won't like -0.1 negative amount. if not, i am going to lose my bitcoins for his fee.

Yes, the only way the prevent it is with multi-sig transactions, which is coming soon.
You can set it to 0, but if the transaction is too "spammy", the client will still send it with the fee.

Hello, every one

i am hosting a bitcoind daemon on my vps, with my apache website, however, i still have few questions about it.


1: in my source code,"$bitcoin = new jsonRPCClient('http://superman:{super}@127.0.0.1:8332/'" here superman is a username,and super is a password, are they the same as wallet encryption function of Bitcoin-Qt? i mean if someone steal the wallet.dat, but he doesn't know this password, can he send any coins out with the wallet.dat? if this is just an independent password of bitcoind daemon, then how can i set up a password for all out going requests just like wallet encryption function of Bitcoin-Qt?

2: if the administrator of my vps, or a hacker hacked in my vps, he got the access of all my files, he saw my source code with the password, then he can steal all my coins with the password right? any other ways to improve the protection of such accidents? (because there are always new vulnerables found, for apache, for linux etc..)

3: how can i know about the translation fee before send bitcoins? ie, if a client has 15btcs in his account, and he send 15btcs out, how can i know how much is the fee of this translation before process it? because it might be free, it might be 0.01btc, it might be 1btc, i need to calculate the amount available before process his request. btw, i don't really get the definition of translation fee, is that obligatory or voluntary? if you pay, your request get faster process by btc network,if not, your request will still be processed, but just slower, right?

thank you for your help