Pages:
Author

Topic: [ANN][SHC] ShinyCoin █First ever RAMHOG algo Pow/Pos █NO ASIC/GPU | Whitepaper - page 20. (Read 58444 times)

newbie
Activity: 50
Merit: 0
Paid   Unconfirmed   Shares   Invalid shares   Efficiency   Hashrate
0.0000 SHC   21.2963 SHC   0.00000011   0.00000000    100%   0.240 H/s

2014-7-6 20:19:23 UTC   4599   0.3614%   1.44559715   immature
2014-7-6 14:51:57 UTC   4541   0.3695%   1.47782832   immature
2014-7-6 12:39:08 UTC   4515   0.4537%   1.81493695   immature
2014-7-6 12:22:27 UTC   4512   0.2456%   0.98243161   immature
2014-7-6 11:01:55 UTC   4494   0.1633%   0.65335552   immature
2014-7-6 10:45:49 UTC   4492   0.3955%   1.58184481   immature
2014-7-6 09:12:16 UTC   4475   0.3953%   1.58128275   immature
2014-7-6 08:31:27 UTC   4467   0.0648%   0.25934443   immature
2014-7-6 05:48:55 UTC   4438   0.3171%   1.26843010   immature
2014-7-6 05:21:55 UTC   4432   0.5426%   2.17044578   immature

Why is always not recognised?  From yesterday to today.
Is it right? Is not supported in the Chinese?
wallet
余额:   0.00  SHC
stak:    0.00  SHC
Mined:  0.00  SHC
未确认:0.00  SHC
交易笔数 0



Yes. It is right.
Mine confirm need about 25 hours~


thank you very munch!
The new mining tool where to download?
The compiled!

Linux standalone miner (thanks to sandor111)
Windows 64-bit standalone miner (thanks to sandor111)

The first thread , you want this?
It has been the authors updated?
full member
Activity: 625
Merit: 100
Paid   Unconfirmed   Shares   Invalid shares   Efficiency   Hashrate
0.0000 SHC   21.2963 SHC   0.00000011   0.00000000    100%   0.240 H/s

2014-7-6 20:19:23 UTC   4599   0.3614%   1.44559715   immature
2014-7-6 14:51:57 UTC   4541   0.3695%   1.47782832   immature
2014-7-6 12:39:08 UTC   4515   0.4537%   1.81493695   immature
2014-7-6 12:22:27 UTC   4512   0.2456%   0.98243161   immature
2014-7-6 11:01:55 UTC   4494   0.1633%   0.65335552   immature
2014-7-6 10:45:49 UTC   4492   0.3955%   1.58184481   immature
2014-7-6 09:12:16 UTC   4475   0.3953%   1.58128275   immature
2014-7-6 08:31:27 UTC   4467   0.0648%   0.25934443   immature
2014-7-6 05:48:55 UTC   4438   0.3171%   1.26843010   immature
2014-7-6 05:21:55 UTC   4432   0.5426%   2.17044578   immature

Why is always not recognised?  From yesterday to today.
Is it right? Is not supported in the Chinese?
wallet
余额:   0.00  SHC
stak:    0.00  SHC
Mined:  0.00  SHC
未确认:0.00  SHC
交易笔数 0



Yes. It is right.
Mine confirm need about 25 hours~


thank you very munch!
The new mining tool where to download?
The compiled!

Linux standalone miner (thanks to sandor111)
Windows 64-bit standalone miner (thanks to sandor111)

The first thread , you want this?
newbie
Activity: 50
Merit: 0
Paid   Unconfirmed   Shares   Invalid shares   Efficiency   Hashrate
0.0000 SHC   21.2963 SHC   0.00000011   0.00000000    100%   0.240 H/s

2014-7-6 20:19:23 UTC   4599   0.3614%   1.44559715   immature
2014-7-6 14:51:57 UTC   4541   0.3695%   1.47782832   immature
2014-7-6 12:39:08 UTC   4515   0.4537%   1.81493695   immature
2014-7-6 12:22:27 UTC   4512   0.2456%   0.98243161   immature
2014-7-6 11:01:55 UTC   4494   0.1633%   0.65335552   immature
2014-7-6 10:45:49 UTC   4492   0.3955%   1.58184481   immature
2014-7-6 09:12:16 UTC   4475   0.3953%   1.58128275   immature
2014-7-6 08:31:27 UTC   4467   0.0648%   0.25934443   immature
2014-7-6 05:48:55 UTC   4438   0.3171%   1.26843010   immature
2014-7-6 05:21:55 UTC   4432   0.5426%   2.17044578   immature

Why is always not recognised?  From yesterday to today.
Is it right? Is not supported in the Chinese?
wallet
余额:   0.00  SHC
stak:    0.00  SHC
Mined:  0.00  SHC
未确认:0.00  SHC
交易笔数 0



Yes. It is right.
Mine confirm need about 25 hours~


thank you very munch!
The new mining tool where to download?
The compiled!
full member
Activity: 625
Merit: 100
Paid   Unconfirmed   Shares   Invalid shares   Efficiency   Hashrate
0.0000 SHC   21.2963 SHC   0.00000011   0.00000000    100%   0.240 H/s

2014-7-6 20:19:23 UTC   4599   0.3614%   1.44559715   immature
2014-7-6 14:51:57 UTC   4541   0.3695%   1.47782832   immature
2014-7-6 12:39:08 UTC   4515   0.4537%   1.81493695   immature
2014-7-6 12:22:27 UTC   4512   0.2456%   0.98243161   immature
2014-7-6 11:01:55 UTC   4494   0.1633%   0.65335552   immature
2014-7-6 10:45:49 UTC   4492   0.3955%   1.58184481   immature
2014-7-6 09:12:16 UTC   4475   0.3953%   1.58128275   immature
2014-7-6 08:31:27 UTC   4467   0.0648%   0.25934443   immature
2014-7-6 05:48:55 UTC   4438   0.3171%   1.26843010   immature
2014-7-6 05:21:55 UTC   4432   0.5426%   2.17044578   immature

Why is always not recognised?  From yesterday to today.
Is it right? Is not supported in the Chinese?
wallet
余额:   0.00  SHC
stak:    0.00  SHC
Mined:  0.00  SHC
未确认:0.00  SHC
交易笔数 0



Yes. It is right.
Mine confirm need about 25 hours~
newbie
Activity: 50
Merit: 0
Paid   Unconfirmed   Shares   Invalid shares   Efficiency   Hashrate
0.0000 SHC   21.2963 SHC   0.00000011   0.00000000    100%   0.240 H/s

2014-7-6 20:19:23 UTC   4599   0.3614%   1.44559715   immature
2014-7-6 14:51:57 UTC   4541   0.3695%   1.47782832   immature
2014-7-6 12:39:08 UTC   4515   0.4537%   1.81493695   immature
2014-7-6 12:22:27 UTC   4512   0.2456%   0.98243161   immature
2014-7-6 11:01:55 UTC   4494   0.1633%   0.65335552   immature
2014-7-6 10:45:49 UTC   4492   0.3955%   1.58184481   immature
2014-7-6 09:12:16 UTC   4475   0.3953%   1.58128275   immature
2014-7-6 08:31:27 UTC   4467   0.0648%   0.25934443   immature
2014-7-6 05:48:55 UTC   4438   0.3171%   1.26843010   immature
2014-7-6 05:21:55 UTC   4432   0.5426%   2.17044578   immature

Why is always not recognised?  From yesterday to today.
Is it right? Is not supported in the Chinese?
wallet
余额:   0.00  SHC
stak:    0.00  SHC
Mined:  0.00  SHC
未确认:0.00  SHC
交易笔数 0

newbie
Activity: 50
Merit: 0
Please give me a good compiler mining software? Thank you.
WIN 64
member
Activity: 71
Merit: 10
Ok so say block 1000's winner sends signed hashes for blocks 1-999. A non-verifying node wouldn't know whether to trust those hashes until he knows that block 1000 is accepted (say when he gets blocks 1000-1006 and they are all valid). But it won't know whether block 1000 is accepted without the hashes from 1-999.

And even if that issue is resolved, block 1000's winner could send incorrect hashes for 1-999 just to mess with the non-verifying nodes.

Is it possible that a node or client cannot verify? It should have the public key. The private key is secret.

EDIT: I'm referring to the current implementation.

By non-verifying I meant one that doesn't compute the hashes.
member
Activity: 71
Merit: 10
Seems like i cant build on ubuntu 12. Anyone has build command?

I'm using
Code:
sudo apt-get update && sudo apt-get install libcurl4-openssl-dev libjansson4 autoconf git make && git clone https://github.com/siklon/shinyminer && cd shinyminer && ./autogen.sh && ./configure CFLAGS="-O3" && make && make install
What error do you get?
Try also installing automake and gcc
hero member
Activity: 658
Merit: 500
Seems like i cant build on ubuntu 12. Anyone has build command?

I'm using
Code:
sudo apt-get update && sudo apt-get install libcurl4-openssl-dev libjansson4 autoconf git make && git clone https://github.com/siklon/shinyminer && cd shinyminer && ./autogen.sh && ./configure CFLAGS="-O3" && make && make install
legendary
Activity: 1092
Merit: 1000
No performance boost on CentOS 6.4/6.5. Cant test on Ubuntu as its a VM..
legendary
Activity: 1092
Merit: 1000
CentOS doesnt, testing the static build, if speed remains the same you should put up a static bin
hero member
Activity: 616
Merit: 500
Shinyminer performance is increased by 25-30%.
https://github.com/siklon/shinyminer
Use following CFLAGS : "-Ofast -funroll-all-loops -march=native"
IMPORTANT - Set hugepages: "sysctl -w vm.nr_hugepages=7680*"

ramhog.c: In function ‘ramhog_thread_pool’:
ramhog.c:38:118: error: ‘MADV_HUGEPAGE’ undeclared (first use in this function)
ramhog.c:38:118: note: each undeclared identifier is reported only once for each function it appears in





What are you compiling on? Ubuntu 13.10 works
legendary
Activity: 1092
Merit: 1000
Shinyminer performance is increased by 25-30%.
https://github.com/siklon/shinyminer
Use following CFLAGS : "-Ofast -funroll-all-loops -march=native"
IMPORTANT - Set hugepages: "sysctl -w vm.nr_hugepages=7680*"

ramhog.c: In function ‘ramhog_thread_pool’:
ramhog.c:38:118: error: ‘MADV_HUGEPAGE’ undeclared (first use in this function)
ramhog.c:38:118: note: each undeclared identifier is reported only once for each function it appears in


EDIT : It wont compile on anything else other than ubuntu.




hero member
Activity: 616
Merit: 500
Shinyminer performance is increased by 25-30%.
https://github.com/siklon/shinyminer
Use following CFLAGS : "-Ofast -funroll-all-loops -march=native"
IMPORTANT - Set hugepages: "sysctl -w vm.nr_hugepages=7680*"
member
Activity: 71
Merit: 10
There's no point for a private key if everybody has it. It'd be the same as if there's no key at all. Then the question is: should a node just blindly trust whatever block other nodes give them? That seems like a bad idea to me.

Why does it have to be a single signature, why can't it be the signature that just won the block so each time the signer would change?
So you want people to trust the miner when he says he made a legit block? No conflict of interest there at all...

What are you talking about?  Any node can claim a winning block and then other nodes will reject if it's not actually valid so what is difference to do it for verifying previous hashes.  In this case the winning node is also at risk of losing his full block reward.
Ok so say block 1000's winner sends signed hashes for blocks 1-999. A non-verifying node wouldn't know whether to trust those hashes until he knows that block 1000 is accepted (say when he gets blocks 1000-1006 and they are all valid). But it won't know whether block 1000 is accepted without the hashes from 1-999.

And even if that issue is resolved, block 1000's winner could send incorrect hashes for 1-999 just to mess with the non-verifying nodes.
newbie
Activity: 42
Merit: 0
There's no point for a private key if everybody has it. It'd be the same as if there's no key at all. Then the question is: should a node just blindly trust whatever block other nodes give them? That seems like a bad idea to me.

Why does it have to be a single signature, why can't it be the signature that just won the block so each time the signer would change?
So you want people to trust the miner when he says he made a legit block? No conflict of interest there at all...

What are you talking about?  Any node can claim a winning block and then other nodes will reject if it's not actually valid so what is difference to do it for verifying previous hashes.  In this case the winning node is also at risk of losing his full block reward.
newbie
Activity: 19
Merit: 0
Trading platform where?

There are several shinycoin mine pool?

Pretty sure not on an exchange yet, although given its popularity will likely happen soon.
newbie
Activity: 50
Merit: 0
Trading platform where?

There are several shinycoin mine pool?
member
Activity: 71
Merit: 10
Who can make Windows 32-bit Qt wallet??

Thanks..
I might be able to do a 32-bit version also... initially I made a 32-bit version but it crashed with even 1 ramhog thread. I guess can't use 15 GB of RAM on the 32-bit version? So I'll make it only work with 0 ramhog threads. Before the latest update there was no point but now there is I guess!
member
Activity: 71
Merit: 10
There's no point for a private key if everybody has it. It'd be the same as if there's no key at all. Then the question is: should a node just blindly trust whatever block other nodes give them? That seems like a bad idea to me.

Why does it have to be a single signature, why can't it be the signature that just won the block so each time the signer would change?
So you want people to trust the miner when he says he made a legit block? No conflict of interest there at all...
Pages:
Jump to: