Topic: [NEW CURRENCY] Maria 2.0 was banned, here is her proof. The birth of Bytecoin! - page 49. (Read 106432 times)
April 02, 2013, 10:32:23 AM
I'm buying 21,000 BTE for 0.1 BTC
April 02, 2013, 10:23:48 AM
I'll spend 1btc if anyone wants to sell. 
April 02, 2013, 10:18:21 AM
.in domain because .com costed too much?
April 02, 2013, 10:06:46 AM
I am having some fun with this coin, and I see from the daemon on my mining server...so are many others..
Watching pushpool with the level 2 debugging and three rigs logged on looks like a free running counter that hiccups every several seconds when a block is found.
Up to id tag 75,824 with 3 rigs in only a couple of hours... That is with no difficultly reduction, the pool is passing the difficulty straight through .
Maybe if I finish the new login and payout code, I could offer the pool publicly. It would be a great opportunity to test the new code in the wild with little risk (in terms of $$).
Code:
"blocks" : 6204,
"connections" : 52,
"proxy" : "",
"difficulty" : 64.00000000,
"connections" : 52,
"proxy" : "",
"difficulty" : 64.00000000,
Watching pushpool with the level 2 debugging and three rigs logged on looks like a free running counter that hiccups every several seconds when a block is found.
Code:
JSON protocol request:
{"method": "getwork", "params": [], "id":75824}
* Re-using existing connection! (#0) with host (nil)
* Connected to (nil) (xxx.xxx.xxx.xxx) port xxxx (#0)
* Server auth using Basic with user 'miner'
> POST / HTTP/1.1
Authorization: Basic xxxxxxxxxxxxxxxxxx
Host: xxx.xxx.xxx.xxx
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 49
* additional stuff not fine transfer.c:1037: 0 0
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
< Date: Tue, 02 Apr 2013 15:15:16 +0000
< Connection: keep-alive
< Content-Length: 596
< Content-Type: application/json
< Server: bitcoin-json-rpc/v0.8.1-2-g7659d51-beta
<
* Connection #0 to host (nil) left intact
JSON protocol response:
{
"error": null,
"result": {
"target": "00000000000000000000000000000000000000000000000000fcff0300000000",
"midstate": "99de493dfb01ac41a314730cbf098f3cecb7abb60968e62587aae8a5a20618a7",
"data": "00000002423ead270e7a4ea606a8b89210ddc8693f0da7c6d195975b0257245800000000e1a6cd6c0c073a9de7d9edfaa0017b715a9613702eb028298510ca8c858fc21f515af6041c03fffc00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000",
"hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"
},
"id": 75824
{"method": "getwork", "params": [], "id":75824}
* Re-using existing connection! (#0) with host (nil)
* Connected to (nil) (xxx.xxx.xxx.xxx) port xxxx (#0)
* Server auth using Basic with user 'miner'
> POST / HTTP/1.1
Authorization: Basic xxxxxxxxxxxxxxxxxx
Host: xxx.xxx.xxx.xxx
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 49
* additional stuff not fine transfer.c:1037: 0 0
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
< Date: Tue, 02 Apr 2013 15:15:16 +0000
< Connection: keep-alive
< Content-Length: 596
< Content-Type: application/json
< Server: bitcoin-json-rpc/v0.8.1-2-g7659d51-beta
<
* Connection #0 to host (nil) left intact
JSON protocol response:
{
"error": null,
"result": {
"target": "00000000000000000000000000000000000000000000000000fcff0300000000",
"midstate": "99de493dfb01ac41a314730cbf098f3cecb7abb60968e62587aae8a5a20618a7",
"data": "00000002423ead270e7a4ea606a8b89210ddc8693f0da7c6d195975b0257245800000000e1a6cd6c0c073a9de7d9edfaa0017b715a9613702eb028298510ca8c858fc21f515af6041c03fffc00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000",
"hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000"
},
"id": 75824
Up to id tag 75,824 with 3 rigs in only a couple of hours...
That is with no difficultly reduction, the pool is passing the difficulty straight through .Maybe if I finish the new login and payout code, I could offer the pool publicly. It would be a great opportunity to test the new code in the wild with little risk (in terms of $$).
April 02, 2013, 09:46:23 AM
Let me say that I really like the idea of an altcurrency that doesn't change anything from the Bitcoin design. I am hoping people stay with this.
Okay so I will be rich with Bytecoins ? Nice.
lol, that's quite a leap of irrational exuberance.
April 02, 2013, 09:45:03 AM
so not even one parameter was changed?
just a copy of Bitcoin?
just a copy of Bitcoin?
Adresses start with 8
Let me say that I really like the idea of an altcurrency that doesn't change anything from the Bitcoin design. I am hoping people stay with this.
Okay so I will be rich with Bytecoins ? Nice.
April 02, 2013, 09:44:45 AM
All the blocks I find are rejected, can someone please explain exactly why is this?
Difficulty is very low at moment. Blocks are being found every few seconds, yours are being orphaned.
Difficulty can only increase at a maximum multiple of 4 every re-target. Next difficulty will be a maximum of 256.
April 02, 2013, 09:40:02 AM
I'll buy anyone a pizza for 10,000 BTE
Seriously
Seriously
April 02, 2013, 09:32:48 AM
Let me say that I really like the idea of an altcurrency that doesn't change anything from the Bitcoin design. I am hoping people stay with this.
April 02, 2013, 09:29:59 AM
The difficulty is now 64.
April 02, 2013, 09:23:12 AM
so not even one parameter was changed?
just a copy of Bitcoin?
just a copy of Bitcoin?
yep, it's an april fool coin!
April 02, 2013, 09:21:57 AM
so not even one parameter was changed?
just a copy of Bitcoin?
just a copy of Bitcoin?
April 02, 2013, 08:32:54 AM
mining this for fun/learning 
All the blocks I find are rejected, can someone please explain exactly why is this?
All the blocks I find are rejected, can someone please explain exactly why is this?
April 02, 2013, 07:38:14 AM
thought i'd try solo mining this using GUIminer on windows for first time, get to the point where i see
Listener for "Default": localhost:9778 02/04/2013 20:56:31, using JSON-RPC (no stratum header)
In the GUIminer console, not sure if its mining ok, does it usually sit like that with no further messages on console ?
( only used to pool mining with much more ouput... )
Try Diablominer and report back [/quote]
Seems to have trouble too, running it on cmnd line with user and pass, and port options, it starts, I get a windows error regarding display driver stopped working, driver seems to recover again ( I figure thats where the miner is hitting the GPU ), and then it just sits there output wise, showing the mhash, accept etc.. all 0's...
April 02, 2013, 07:36:14 AM
Could someone spend some bytecoins, please? I'll program a little casino (dice play) website for this new coin but can't mine on the server atm. I think my website requires at least 100 ByteCoins.
8UK7ytotGZA4LiAcEedowMidVmaPkaxuMK
thxs
8UK7ytotGZA4LiAcEedowMidVmaPkaxuMK
thxs
April 02, 2013, 07:27:52 AM
As I understand, this shortcut should start as SERVER, but it opens standard client wallet app... So what am I missing?
You can add a -server flag to the shortcut to force it into server mode at runtime.
That didn't help... If I omit pass/login, it complains about it... but when all is correctly set, just basic wallet opens.
April 02, 2013, 07:16:04 AM
When I try to solo mine I get this error in GUIMiner
[Errno 10061] No connection could be made because the target machine actively refused it
[Errno 10061] No connection could be made because the target machine actively refused it
Are you using the right port?
April 02, 2013, 07:11:23 AM
When I try to solo mine I get this error in GUIMiner
[Errno 10061] No connection could be made because the target machine actively refused it
[Errno 10061] No connection could be made because the target machine actively refused it
I had that error at first too..
It could be your firewall blocking, or passwd not correct somewhere etc..
check this howto also - https://bitcointalksearch.org/topic/solo-mining-with-gui-miner-123564
April 02, 2013, 07:09:48 AM
[/quote]
thought i'd try solo mining this using GUIminer on windows for first time, get to the point where i see
Listener for "Default": localhost:9778 02/04/2013 20:56:31, using JSON-RPC (no stratum header)
In the GUIminer console, not sure if its mining ok, does it usually sit like that with no further messages on console ?
( only used to pool mining with much more ouput... )
Try Diablominer and report back.
April 02, 2013, 07:07:43 AM
When I try to solo mine I get this error in GUIMiner
[Errno 10061] No connection could be made because the target machine actively refused it
[Errno 10061] No connection could be made because the target machine actively refused it
Jump to: