Topic: Terra Coin (Read 4342 times)

I have some sapphires which I overclock to 900mhz or so I believe.  I run one card with -f60 for desktop and the other -f0 I think I get about 340 and 370 mhs respectively.  I even play games with the card mining...

I havent used it in a few days, but I think I was getting 20 coins every 45 min or so solo mining with dual 6950 radeons...

Aside from having those lines in terracoin.conf file and restarting client to get it running in server mode, you should set Coinotron or BitcoinReactor
as secondary pool. That way you will leech long-polling data from them, which will make your Terracoin server update block as soon as one of those
pools detect the change, but more importantly, it will update data your miner is working on. Unless there is long-polling info from somewhere, your
miner could be working on old block for up to scantime seconds, which is 60 by default! Any block solution submitted by miner in such scenario will
be rejected by Terracoin server. Also, check if your miner is set to failover-only disabled mode = enabled mode is bugged and might make miner lag
around 25 seconds behind block change even with long-polling data received!

Aside from having those lines in terracoin.conf file and restarting client to get it running in server mode, you should set Coinotron or BitcoinReactor
as secondary pool. That way you will leech long-polling data from them, which will make your Terracoin server update block as soon as one of those
pools detect the change, but more importantly, it will update data your miner is working on. Unless there is long-polling info from somewhere, your
miner could be working on old block for up to scantime seconds, which is 60 by default! Any block solution submitted by miner in such scenario will
be rejected by Terracoin server. Also, check if your miner is set to failover-only disabled mode = enabled mode is bugged and might make miner lag
around 25 seconds behind block change even with long-polling data received!

server=1
rpcuser=somenickname
rpcpassword=somestrongpassword
rpcallowip=127.0.0.1
rpcport=18332

what port does this use for soloing and what is needed in config ?

Why do you mine in a pool for TRC?  Seems like solo is fine...

addition to previous idea: "return" button (cancel transaction or whatever) to every transaction
great for shops for refunds???

I think those are prety simple to do, but how the fuck can i contact terracoin devs???

So the relatively simple fix.   bitcoind should have a delay send feature.  An parameter which when set in configfile indicates the number of seconds a transaction should be held before sending.
Code:

delaysend=120


Before someone freaks out about "reversing payments" this would simply be client side.   (assuming delaysend=120 is set)
1) user sends x BTC to address y (x or y may be wrong)
2) client provides transaction id
3) for the next 120 seconds the tx is NOT broadcast to the network.  
4a) In the GUI a cancel button can be shown (which disapears after tx is broadcast).
4b) In bitcoind a new two new RPCs are added.
Code:

CancelDelaySend [txid].  txid is optional.  Calling it with no txid will abort all queued delay sends
OverrideDelaySend [walletpassphrase].  Wallet passphrase is required even if wallet is unlocked (see hot wallet below).

5) delaysend expires and tx is broadcast normally

Honestly I would put some coins towards a bounty (a portion for a functional patch, and another portion when included in mainline).

This would also provide some (although not complete) protection for a hot wallet.
1) hot-wallet password is NOT stored on server.
2) hot-wallet password manually entered by admin when bitcoind is started (with no expiration on locking hot-wallet)
3) DelaySend can't be modified once bitcoind is started.  changing it requires bitcoind reset (and thus admin password).
4) DelaySend can be overridden but requires admin password.