-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
12 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good work till.....maybe you need swap.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i was just gussing..... i thought that pow limit exceed ...so; if one want to change past ...he need a new blockchain.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so; you made pos/pow hybrid ...
This will increase change of collision as have 2 proofs ...pow and pos ..
Suppose block time is 30sec. and in 30 a pos block found , and at that time pow also found, but network can have only one block so one should be rejected ..every 30 sec. This may cause a lot of orphane blocks.
And most generally pow block get rejected as pos have large community to verify it.
lol...
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work till it will not have any orphan block (your new project) as you already told have different timings for pos &pow .
So, no problem of time clash=no rejection (no orphan block)
nice till you already solved problem.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this problem occurs in coins having same timing of pos pow
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Tillkoeln ,
I have cloned a POS coin but now i am unable to generate the first block.
Please tell me how to do that
i am in a big problem .
if you help me , then i will be very greatfull
Thanks in advance
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i would go this way...
start the client 2 times.... which require 2 different folders for the data etc....
open the cmd prompt inside your executable.
mkdir c:\yourcoin1
mkdir c:\yourcoin2
yourcoin-qt.exe -datadir=C:\yourcoin1 -server=1 -rpcpassword=123 -rpcuser=123 -rpcport=12345 -port=54321
yourcoin-qt.exe -datadir=C:\yourcoin2 -server=1 -rpcpassword=1234 -rpcuser=1234 -rpcport=23456 -port=65432 -addnode=127.0.0.1:54321
.. this should start 2 instances for your coin with different folders....
now use a simple cpu miner like "cpuminer-multi-rel1.1"
modify the conf file for the miner :
and run the miner *exe
then just wait... if anything is red = bad
anything else is a good sign
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vickyzare567 , you need to mine genesis block, and as far as I know it would be POW block
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db03106
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.