|
ah, i forgot,
it's not the server doing the math/rounding/tell what amount to send, it's your script.
that's great and indeed a workaround lost sub-cents, the server actually doesnt know about sub-cents.
|
|
|
|
Threshold makes sense, don't send coins until I have X many. same subject: is it planned to only send coins >0.01? so if i have reward:0.01675429 i only get 0.01 and the sub-cents stay where they are? else i will lose the sub-cents as soon as i send those 0.01 to anyone (if that's the only cent i'v got). nevermind, that doesnt even make sense, the sub-cents will be lost when splitting those 0.01 to send anyway |
|
|
|
i need a portable file to run on certain computers just "install" it once and copy the folder to your thumbdrive, works fine for me (note that i only used 0.2.1, newer versions slow 4way down on my phenomX3). |
|
|
|
how the exclusivity benefits the market at all there's no such thing as exclusivity, anyone, yes, you too, is able to buy some decent hardware and start mining immediately. i myself just ordered a new gfx-cad today only for the good of the bitcoin-network (and maybe, if i'm lucky, some coins for myself). if anyone who created a new bitcoin account was given 100 bitcoins and how would you tell, if that person has an "account" and got his 100btc already, or not? there's no way you can tell, how many bitcoin-clients i installed, should i get 100 for each instance? and those "early adopters" took a high risk by investing (energy,time and money) early, when they'v been able to generate the equivalent of hundreds, if not thousands of bitcoins, those coins had almost no value at all. take your risk now (it's still high) and invest (in coins, or hardware+energy), or don't, but don't blame those who did and will do. |
|
|
|
|
no big deal to use jgarzik's "installer",
it'll just create a new folder of your choice (and shortcuts if you wish) and unpack a few files to it,
nothing to worry about.
|
|
|
|
which miner do you use? m0mchil's: poclbm --host=mining.bitcoin.cz --port=8332 --user=<name.workerN> --pass=<yourpass> --device=N jgarzik's: minerd --url=http://mining.bitcoin.cz:8332 --userpass=<name.workerN:yourpass> --algo=<4way> --threads=N not sure about Diablos, something similar i guess.  |
|
|
|
|
yay, seems like we already solved our 2nd block.
are worker-stats updated when generations are matured?
cuz they still show 0 found blocks.
|
|
|
|
|
works nicely with jgarzik's CPU (only tested 0.2.1) and m0mchils GPU miner,
it seems so at least, workers share-count shows what miners tell.
hashcount is pretty much the same as on local getwork-servers, now we just need to solve some blocks to see if it pays.
|
|
|
|
|
i got no response so far.
|
|
|
|
it's necessary to use Tor's MapAddress option. Does I2P's proxy have a similar option of mapping an I2P address to an IP address? good question, that's exactly where i'm stuck. i set up one i2p-node, created a server-tunnel on port 8333 and just started a bitcoin-client that is connected to my main-client (and 7 others, not using a proxy). now i'm trying to connect to that bitcoin-node through i2p, so i set up a second i2p-node, added the host and target from first node to its addressbook, set up a socks-tunnel, set bitcoin to use the socks. but now what? have to -addnode my 1st node somehow, but i'v no idea how. update: played around a bit more, but my bestest result so far was just a one-way connection. set up a standard-client-tunnel pointing to first-node.i2p, using it as proxy instead of socks on the second i2p-node, bitcoin tries to connect, but fails, connections go from 8 to 9, back to 8 to 9 to 8 ..... on first node, second stays at 0. here's snippets of debug.logs: first node ...
accepted connection
sending: version (85 bytes)
MainFrameRepaint
socket closed
disconnecting node
DelayedRepaint
socket closed
disconnecting node
MainFrameRepaint
accepted connection
sending: version (85 bytes)
MainFrameRepaint
DelayedRepaint
socket closed
disconnecting node
... second node ...
proxy connecting
ERROR: Proxy returned error -66
... if anyone figures out, what todo to make it work, let me know and i'll set it up and leave it running. |
|
|
|
|
yes, your bitcents are generated on that address of yours,
they are not send by the server.
the glory of the pool.
|
|
|
|
Yepp, somewhere... but where is this "somewhere"? Not in my wallet.dat, yet. my guess, in MyBitcoins wallet. i'm not sure how MyBitcoin checks your account balance, i havent used my account ever, but if they just check your funding-address/es for received coins, those generated coins might not show up on your account, cuz they haven't been received, but generated. i'm curious about their response. |
|
|
|
as you can see here your address received 0.09btc. those have to be somewhere. |
|
|
|
|
your bitcoin-client downloads the blocks as soon as you are connected.
on your screenshot, you are not connected to any other nodes (statusbar: (not connected) 0 connections) and dont have any blocks (0 blocks) downloaded.
your client will not start generating until it has downloaded all blocks (currently 97239).
i'm not sure why you are not connected, seems something is still blocking bitcoin-connections (firewall/router).
you might wanna try to connect through TOR to walkaround some fences.
|
|
|
|
This feature exists to improve anonymity. this feature exists. you might use it to improve anonymity. but you can also use a single donation-address for the rest of your (or your projects) lifetime, why not? people know, who they're donating to anyway, don't they? and it even prooves to everyone how much donations have been received by that address/project, which might be good or bad, depending on who you ask/are. |
|
|
|
nice that there seems to be an OpenCL miner available now, sad though, that it doesnt work (for me on Nvidia at least). ...snip...
<program source>:140:3: error: call to 'rotate' is ambiguous
sharound(E,F,G,H,A,B,C,D,R(36),0x650A7354);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<program source>:47:123: note: instantiated from:
#define sharound(a,b,c,d,e,f,g,h,x,K) {t1=h+(rotateright(e,6)^rotateright(e,11)^
rotateright(e,25))+(g^(e&(f^g)))+K+x; t2=(rotateright(a,2)^rotateright(a,13)^rot
ateright(a,22))+((a&b)|(c&(a|b))); d+=t1; h=t1+t2;}
^
<program source>:45:30: note: instantiated from:
#define rotateright(x,bits) (rotate(x,32-bits))
^~~~~~
<built-in>:2967:24: note: candidate function
ulong __OVERLOADABLE__ rotate(ulong, ulong);
^
<built-in>:2966:23: note: candidate function
long __OVERLOADABLE__ rotate(long, long);
^
<built-in>:2965:23: note: candidate function
uint __OVERLOADABLE__ rotate(uint, uint);
^
<built-in>:2964:22: note: candidate function
int __OVERLOADABLE__ rotate(int, int);
^
<built-in>:2963:25: note: candidate function
ushort __OVERLOADABLE__ rotate(ushort, ushort);
^
<built-in>:2962:24: note: candidate function
short __OVERLOADABLE__ rotate(short, short);
^
<built-in>:2961:24: note: candidate function
uchar __OVERLOADABLE__ rotate(uchar, uchar);
^
<built-in>:2960:23: note: candidate function
char __OVERLOADABLE__ rotate(char, char);
^
<program source>:141:3: error: call to 'rotate' is ambiguous
sharound(D,E,F,G,H,A,B,C,R(37),0x766A0ABB);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<program source>:47:46: note: instantiated from:
#define sharound(a,b,c,d,e,f,g,h,x,K) {t1=h+(rotateright(e,6)^rotateright(e,11)^
rotateright(e,25))+(g^(e&(f^g)))+K+x; t2=(rotateright(a,2)^rotateright(a,13)^rot
ateright(a,22))+((a&b)|(c&(a|b))); d+=t1; h=t1+t2;}
^
<program source>:45:30: note: instantiated from:
#define rotateright(x,bits) (rotate(x,32-bits))
^~~~~~
<built-in>:2967:24: note: candidate function
ulong __OVERLOADABLE__ rotate(ulong, ulong);
^
<built-in>:2966:23: note: candidate function
long __OVERLOADABLE__ rotate(long, long);
^
<built-in>:2965:23: note: candidate function
uint __OVERLOADABLE__ rotate(uint, uint);
^
<built-in>:2964:22: note: candidate function
int __OVERLOADABLE__ rotate(int, int);
^
<built-in>:2963:25: note: candidate function
ushort __OVERLOADABLE__ rotate(ushort, ushort);
^
<built-in>:2962:24: note: candidate function
short __OVERLOADABLE__ rotate(short, short);
^
<built-in>:2961:24: note: candidate function
uchar __OVERLOADABLE__ rotate(uchar, uchar);
^
<built-in>:2960:23: note: candidate function
char __OVERLOADABLE__ rotate(char, char);
^
<program source>:141:3: error: call to 'rotate' is ambiguous
sharound(D,E,F,G,H,A,B,C,R(37),0x766A0ABB);
...snip...
the CUDA client doesnt show its best hashes anymore, loads the GPU a bit more (50%->65%) what makes it a bit faster hashing (gtx260: 18M->25M), but it also loads the CPU more than before (50%->75%). |
|
|
|
when your parents do, you make profit anyway.  so you pay half a coin per kW/h, consumed 10.8kW/h 0.5x10.8= 5.4btc so far you "earned" 3btc, so you made a loss. not to mention that you paid for hardware, but also may use that system otherwise. |
|
|
|
|
hard to say,
we don't know what you have to pay for 10.8kW/h
|
|
|
|
|
bitcoin itself is secure,
its other payment methods that scammers use to "chargeback" what they payed you,
or your faith in them, when you payed in advance.
if you send your money to someone you dont trust, or have never met,
this person might take your money and leave without giving you what you payed for.
bitcoin is like cash, if you give it away, its gone, there are no chargebacks or other ways to get your money back.
|
|
|
|
|
Show Posts
