New win-64 wallet works well.
How about any plan of exchange?
Topic: [ANN][SHC] ShinyCoin █First ever RAMHOG algo Pow/Pos █NO ASIC/GPU | Whitepaper - page 21. (Read 58457 times)
July 06, 2014, 02:47:17 AM
July 06, 2014, 02:20:00 AM
Who can make Windows 32-bit Qt wallet??
Thanks..
Thanks..
July 06, 2014, 02:16:19 AM
Chinese translation updated.
By the way, Due to dropbox banned in China, Share another downlink: http://pan.baidu.com/s/1pNWVO
By the way, Due to dropbox banned in China, Share another downlink: http://pan.baidu.com/s/1pNWVO
July 06, 2014, 02:10:30 AM
Quote
I think in the end you will still have to invent a way for the nodes to trust each other so as to be sure about what is valid and what is invalid. I'm not sure this is possible by re-using the keypair that is used for signing/verifying the hashes, unless I am missing something here...
Why not?
Well, I'm not saying it can't be used for node verification.
But which nodes would have the authority to ban other nodes for distributing hashes with invalid signatures?
1) If you go ahead with a centralized infrastructure with 10-20 signing nodes (only those have the private key), then this problem is solved, as long as those signing nodes can be fully protected.
Quote
2) On the contrary, if you go ahead with a decentralized infrastructure, aka distribute the private key to all clients & nodes so they are all signing nodes, a client can still verify the signed hashes using the relevant public key and tell if the node is distributing valid hashes or not. Problem in this case is which nodes would have the authority to ban invalid nodes. As I see it, you need a second layer of trust or a type of voting system, with which a node gets banned if it gets 10 negative votes from clients or something like that.
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?
July 06, 2014, 02:08:05 AM
Quote
I think in the end you will still have to invent a way for the nodes to trust each other so as to be sure about what is valid and what is invalid. I'm not sure this is possible by re-using the keypair that is used for signing/verifying the hashes, unless I am missing something here...
Why not?
Well, I'm not saying it can't be used for node verification.
But which nodes would have the authority to ban other nodes for distributing hashes with invalid signatures?
1) If you go ahead with a centralized infrastructure with 10-20 signing nodes (only those have the private key), then this problem is solved, as long as those signing nodes can be fully protected.
Quote
2) On the contrary, if you go ahead with a decentralized infrastructure, aka distribute the private key to all clients & nodes so they are all signing nodes, a client can still verify the signed hashes using the relevant public key and tell if the node is distributing valid hashes or not. Problem in this case is which nodes would have the authority to ban invalid nodes. As I see it, you need a second layer of trust or a type of voting system, with which a node gets banned if it gets 10 negative votes from clients or something like that.
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. July 06, 2014, 02:05:44 AM
Quote
Let's say the node with the winning block is the signer of verifying the previous hashes. When the node attempts to relay the information not only is his winning block invalid because the signature for verifying the hashes are invalid but also by default all nodes receiving invalid info will be default block the IP address of any node trying to send or relay invalid hashes. Am I missing something?
yeah you're missing the code that should be attached showing how you're going to accomplish this. I also don't understand why any of this is relevant.
July 06, 2014, 01:57:04 AM
Quote
I think in the end you will still have to invent a way for the nodes to trust each other so as to be sure about what is valid and what is invalid. I'm not sure this is possible by re-using the keypair that is used for signing/verifying the hashes, unless I am missing something here...
Why not?
Well, I'm not saying it can't be used for node verification.
But which nodes would have the authority to ban other nodes for distributing hashes with invalid signatures?
1) If you go ahead with a centralized infrastructure with 10-20 signing nodes (only those have the private key), then this problem is solved, as long as those signing nodes can be fully protected.
2) On the contrary, if you go ahead with a decentralized infrastructure, aka distribute the private key to all clients & nodes so they are all signing nodes, a client can still verify the signed hashes using the relevant public key and tell if the node is distributing valid hashes or not. Problem in this case is which nodes would have the authority to ban invalid nodes. As I see it, you need a second layer of trust or a type of voting system, with which a node gets banned if it gets 10 negative votes from clients or something like that.
Let's say the node with the winning block is the signer of verifying the previous hashes. When the node attempts to relay the information not only is his winning block invalid because the signature for verifying the hashes are invalid but also by default all nodes receiving invalid info will be default block the IP address of any node trying to send or relay invalid hashes. Am I missing something?
July 06, 2014, 01:22:55 AM
Download the wallet, and change config file to ramhogthreads=1
gen=1
Please send a detailed steps,thanks!gen=1
download windows wallet from
https://www.dropbox.com/s/chgg78pxys7lodh/ShinyCoin-Qt-Win64-v0.3.0.zip
change config file to
ramhogthreads=1
gen = 1
Create a new file, called ShinyCoin.conf. as follows:
ramhogthreads=1
gen = 1
Copy this file to the%appdata% ShinyCoin
Then run the wallet?
July 06, 2014, 12:26:42 AM
Download the wallet, and change config file to ramhogthreads=1
gen=1
Please send a detailed steps,thanks!gen=1
download windows wallet from
https://www.dropbox.com/s/chgg78pxys7lodh/ShinyCoin-Qt-Win64-v0.3.0.zip
change config file to
ramhogthreads=1
gen = 1
July 05, 2014, 11:18:35 PM
Download the wallet, and change config file to ramhogthreads=1
gen=1
gen=1
Please send a detailed steps，thanks!
July 05, 2014, 11:17:14 PM
Although the difficulty on the network is crazy high so you might get annoyed for days without blocks, so probably a pool is better.
July 05, 2014, 11:07:30 PM
Download the wallet, and change config file to ramhogthreads=1
gen=1
gen=1
July 05, 2014, 10:42:50 PM
solo???
How to solo?
How to solo?
July 05, 2014, 10:32:32 PM
Solo Mine
July 05, 2014, 10:22:48 PM
CPU:AMD 8350
Memory：Kingtong 4g*4=16G
C:\Users\Administrator\Desktop\S\工具shinyminer>shinyminer -o stratum+tcp://106.3.225.46:6666 -O STuuFKs5UBfyFXv11RWbiyeuipA9k9Seau:x -t 1
[2014-07-06 11:01:19] Starting Stratum on stratum+tcp://106.3.225.46:6666
[2014-07-06 11:01:19] 1 miner threads started, using 'ramhog' algorithm.
[2014-07-06 11:03:23] Stratum requested work restart
[2014-07-06 11:04:31] Stratum requested work restart
[2014-07-06 11:06:47] thread 0: 2 hashes, 0.37 hash/m
[2014-07-06 11:09:08] Stratum requested work restart
[2014-07-06 11:10:46] thread 0: 2 hashes, 0.50 hash/m
[2014-07-06 11:11:42] stratum_recv_line failed
[2014-07-06 11:11:51] Stratum connection interrupted
[2014-07-06 11:13:23] thread 0: 1 hashes, 0.38 hash/m
Normal?
What should I do?
Memory：Kingtong 4g*4=16G
C:\Users\Administrator\Desktop\S\工具shinyminer>shinyminer -o stratum+tcp://106.3.225.46:6666 -O STuuFKs5UBfyFXv11RWbiyeuipA9k9Seau:x -t 1
[2014-07-06 11:01:19] Starting Stratum on stratum+tcp://106.3.225.46:6666
[2014-07-06 11:01:19] 1 miner threads started, using 'ramhog' algorithm.
[2014-07-06 11:03:23] Stratum requested work restart
[2014-07-06 11:04:31] Stratum requested work restart
[2014-07-06 11:06:47] thread 0: 2 hashes, 0.37 hash/m
[2014-07-06 11:09:08] Stratum requested work restart
[2014-07-06 11:10:46] thread 0: 2 hashes, 0.50 hash/m
[2014-07-06 11:11:42] stratum_recv_line failed
[2014-07-06 11:11:51] Stratum connection interrupted
[2014-07-06 11:13:23] thread 0: 1 hashes, 0.38 hash/m
Normal?
What should I do?
July 05, 2014, 10:00:05 PM
Lost 2002.99shc
From SZ9ZweWz3ZNVUMgZwS5VGgrCP4xdQ7opoQ to SW87Vv6qGWwMSkX43nTwAt2RVyyVk3epH2 lost 2002.99shc, the latest data synchronization, still have not received
help
From SZ9ZweWz3ZNVUMgZwS5VGgrCP4xdQ7opoQ to SW87Vv6qGWwMSkX43nTwAt2RVyyVk3epH2 lost 2002.99shc, the latest data synchronization, still have not received
help
July 05, 2014, 09:28:05 PM
Thank you！
I was in the China Internet.
Can't open。
The software solves
My grammar is not good
I was in the China Internet.
Can't open。
The software solves
My grammar is not good
July 05, 2014, 09:09:23 PM
Who can give me a address which can download the wallet？
https://www.dropbox.com/s/chgg78pxys7lodh/ShinyCoin-Qt-Win64-v0.3.0.zip July 05, 2014, 09:00:13 PM
Who can give me a address which can download the wallet？
July 05, 2014, 08:52:51 PM
And could someone bring me a ShinyCoin Wallet?
Can't find a place to download
win 64
Can't find a place to download
win 64
Its on the opening post ... Windows binaries
Jump to: