I deleted because I realised you are so fucking dumb that you won't realise what mistake you did. Now fuck off!
LMAO yea ok you think that 
Topic: * (Read 2391 times)
I said the same thing like 5 posts ago LMAO stupid people are stupid
yes just in your bitcoin.conf add
Code:
server=1
Yes of course you need to add a user name and password that is how RPC works, otherwise how would you connect
Now fuck off, faggot!
is it possible to run GUI and server mode in combination?
yes just in your bitcoin.conf add
Code:
server=1
No you GTFO and STFU, server mode is server=1, but now your the guru LMAO
AWWW he deleted his rude comments
It's happening with all versions of binaries I've download and used by now, and with both Bitcoin and Terracoin clients. No other
software I used ever behaved that same way - some do attampt to modify other apps memory and so on, but not prior to some
user action, and not periodicaly and in persistent fashion.
software I used ever behaved that same way - some do attampt to modify other apps memory and so on, but not prior to some
user action, and not periodicaly and in persistent fashion.
Those reports make no sense at all— each process has its own address space. It's not possible to even _attempt_ to modify another process without invoking a bunch of OS calls to get access to the other processes space (of course, bitcoin has no code to do any of that). Unfortunately those reports also include no details so I have no idea what behavior its mistaking.
Are you sure you don't have some kind of infection on that system?
No one gives a shit or what?
It might just be a bug? You'd have to dig deeper.
Does this happen with version you compiled from source or binary you downloaded?
You missunderstood my question. By default client I mean one with GUI but without any additional settings. What I want to know is
what's the difference running GUI client without and one with server=1, in terms of usefulness for other nodes. In other words, do I
help network more if I run client as server, but I don't solo mine with it, or via some other miner software.
Also, what's the difference when running client with just server=1 and with all this commands:
server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
?
As this is potentially dangerous (you can send bitcoins with it), you can - and should - restrict access by using the rpcuser, rpcpassword and rpcallowip settings.
In terms of usefullness to other bitcoin nodes: there is no benefit at all, as other nodes only use the standard bitcoin protocol to send/receive messages from each other.
So again, don't enable the server=1 if you don't need programmatic access to your bitcoin client.
Just to be clear: from the side of the P2P network there is no difference between running bitcoind, Bitcoin-Qt, or Bitcoin-Qt -server. The only thing that changes between these modes of operation is how you access the block chain and wallet data.
Each of them implements the zero-trust model a full node brings (i.e. it verifies all data received from the network, relays what is valid, and ignores what isn't). If you want a more lightweight node, look at SPV clients like MultiBit or Bitcoin Wallet for Android, which only verify the block headers, but assumes that transactions in the best chain are valid. You can go even more lightweight, by not running a network node at all, but trust all data they receive from a server, like Electrum or several other smartphone applications do.
Each of them implements the zero-trust model a full node brings (i.e. it verifies all data received from the network, relays what is valid, and ignores what isn't). If you want a more lightweight node, look at SPV clients like MultiBit or Bitcoin Wallet for Android, which only verify the block headers, but assumes that transactions in the best chain are valid. You can go even more lightweight, by not running a network node at all, but trust all data they receive from a server, like Electrum or several other smartphone applications do.
Jump to: