thanks i mean I developed my own pos coin, after the pow coins mined, there is no new blocks so sync is lost, how to let the new block generated faster? Adjust minStateAge parameter? Or any way to let the new block created faster in pos
|
|
|
When does the interest generated? How to sync? After pow coins mined, how to mine the pos coins and which parameter to adjust in order to generate new pos blocks fast? Thanks
|
|
|
I made a coin of x11+pos! right now it has passed x11, all pow coins mined, right now only left pure pos coins, how can I mine and keep adding new blocks? Just keep wallet open? It looks like the interest will be generated after a fixed time? Which parameter to adjust for popcoin ? Thanks
|
|
|
thanks。actually x11 is only pow period, after all the pow coins mined, only pos coins left, during this pos period, I cannot use x11 miner any more, it has to be something else to generate new blocks, how to mine in pure pos?
|
|
|
I tried several pure pos coins, after most of the coins mined during pow period, no new blocks added since no mining, also the interest of stake not generated, how to make the sync fast? Thanks
|
|
|
thanks the problem is the x11 wallet does not support this command I am thinking to use pure pos but how to make the wallet sync
|
|
|
I finished POW X11 and start POS,state min age=2 min based ppcoin
I setup one node, pure POS, and minage=2 min, after POW, doing some local transactions to my self, I found the transactions not show up in blockchain, that means, not broadcat to the node, also, no stake interest genarated, also no new block added, in debug no strange message, it must wait 2 min to generate interest or 24 hrs?
the POS interest not generated also the local transactions to my self not posted, debug:
keypool added key 118, size=101 CommitTransaction: CTransaction(hash=f0d8ed6c77, nTime=1434537086, ver=1, vin.size=4, vout.size=2, nLockTime=0) CTxIn(COutPoint(1436c7a90c, 0), scriptSig=30440220290a8bc5c368c44a) CTxIn(COutPoint(1436c7a90c, 1), scriptSig=30450221008559ace60c4b0b) CTxIn(COutPoint(2e244509f1, 1), scriptSig=30450221009ea794f9a39a56) CTxIn(COutPoint(ac477d1423, 1), scriptSig=3045022100dfc2c36b7f64e5) CTxOut(nValue=0.01197, scriptPubKey=OP_DUP OP_HASH160 7c8d32bbc3227ebcb36bc6f845f2668b9b51a993 OP_EQUALVERIFY OP_CHECKSIG) CTxOut(nValue=0.009, scriptPubKey=OP_DUP OP_HASH160 42b190a1a84c8085064c8e7a48d8e3b90eb2f913 OP_EQUALVERIFY OP_CHECKSIG) AddToWallet f0d8ed6c77 new WalletUpdateSpent found spent coin 0.01298 SUM 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 NotifyTransactionChanged 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 status=1 WalletUpdateSpent found spent coin 0.01298 SUM 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 NotifyTransactionChanged 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 status=1 WalletUpdateSpent found spent coin 0.99999 SUM 2e244509f1b6a792db55d1055d782a04bb80217df8c1c36aec40f8fa963d6174 NotifyTransactionChanged 2e244509f1b6a792db55d1055d782a04bb80217df8c1c36aec40f8fa963d6174 status=1 WalletUpdateSpent found spent coin 0.01499 SUM ac477d1423a522fb6de176cacdd1d0a71588f3afca5b3a98938a3efa9b7cd65a NotifyTransactionChanged ac477d1423a522fb6de176cacdd1d0a71588f3afca5b3a98938a3efa9b7cd65a status=1 NotifyTransactionChanged f0d8ed6c77bff14842bd40e1ee772b554b2c7a86e6e2b69c9f1073143912d6da status=0 NotifyTransactionChanged 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 status=1 NotifyTransactionChanged 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 status=1 NotifyTransactionChanged 2e244509f1b6a792db55d1055d782a04bb80217df8c1c36aec40f8fa963d6174 status=1 NotifyTransactionChanged ac477d1423a522fb6de176cacdd1d0a71588f3afca5b3a98938a3efa9b7cd65a status=1 CTxMemPool::accept() : accepted f0d8ed6c77 (poolsz 15) Relaying wtx f0d8ed6c77 updateWallet 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 1 inWallet=1 inModel=1 Index=5-6 showTransaction=1 derivedStatus=1 updateWallet 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 1 inWallet=1 inModel=1 Index=5-6 showTransaction=1 derivedStatus=1 updateWallet 2e244509f1b6a792db55d1055d782a04bb80217df8c1c36aec40f8fa963d6174 1 inWallet=1 inModel=1 Index=10-11 showTransaction=1 derivedStatus=1 updateWallet ac477d1423a522fb6de176cacdd1d0a71588f3afca5b3a98938a3efa9b7cd65a 1 inWallet=1 inModel=1 Index=34-35 showTransaction=1 derivedStatus=1 updateWallet f0d8ed6c77bff14842bd40e1ee772b554b2c7a86e6e2b69c9f1073143912d6da 0 inWallet=1 inModel=0 Index=48-48 showTransaction=1 derivedStatus=0 updateWallet 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 1 inWallet=1 inModel=1 Index=5-6 showTransaction=1 derivedStatus=1 updateWallet 1436c7a90c7033ab985b450035232f33a6a4a0e000e3f07d1f19cac2c109fe93 1 inWallet=1 inModel=1 Index=5-6 showTransaction=1 derivedStatus=1 updateWallet 2e244509f1b6a792db55d1055d782a04bb80217df8c1c36aec40f8fa963d6174 1 inWallet=1 inModel=1 Index=10-11 showTransaction=1 derivedStatus=1 updateWallet ac477d1423a522fb6de176cacdd1d0a71588f3afca5b3a98938a3efa9b7cd65a 1 inWallet=1 inModel=1 Index=34-35 showTransaction=1 derivedStatus=1 received getdata for: tx f0d8ed6c77bff14842bd Flushing wallet.dat Flushed wallet.dat 93ms keypool added key 119, size=101 Flushing wallet.dat Flushed wallet.dat 172ms Flushed 1 addresses to peers.dat 62ms
|
|
|
for the commands, whether I need to run one of them or I need to run all of them? for example, only run Berkeley DB commands or only run openssl ?
OpenSSL ------- MSYS shell: un-tar sources with MSYS 'tar xfz' to avoid issue with symlinks (OpenSSL ticket 2377) change 'MAKE' env. variable from 'C:\MinGW32\bin\mingw32-make.exe' to '/c/MinGW32/bin/mingw32-make.exe'
cd /c/openssl-1.0.1b-mgw ./config make
Berkeley DB ----------- MSYS shell: cd /c/db-4.8.30.NC-mgw/build_unix sh ../dist/configure --enable-mingw --enable-cxx make
Boost ----- DOS prompt: downloaded boost jam 3.1.18 cd \boost-1.47.0-mgw bjam toolset=gcc --build-type=complete stage
MiniUPnPc --------- UPnP support is optional, make with USE_UPNP= to disable it.
MSYS shell: cd /c/miniupnpc-1.6-mgw make -f Makefile.mingw mkdir miniupnpc cp *.h miniupnpc/
BlackCoin ------- DOS prompt: cd \e-goldcoin\src mingw32-make -f makefile.mingw strip egdd.exe
|
|
|
it shows: c:/mingw/bin/../lib/gcc/ming32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_thread_win32-mgw46-mt-s-1_54 collect2: ld 1
|
|
|
I try to compile a coin wallet under windows, https://github.com/E-gold-team/e-goldcoinI tried to compile it by several ways, it always shows some error, I did not change anything, I use msys shell, by command: $qmake litecoinx-qt.pro RELEASE=1 USE_UPNP=1 -config release QMAKE_LFLAGS+= "-static-libgcc -static-libstdc++" BOOST_INCLUDE_PATH=C:/MinGW/msys/1.0/local/include BOOST_LIB_PATH=C:/MinGW/msys/1.0/local/lib BOOST_LIB_SUFFIX=-mgw46-mt-s-1_54 $make -f Makefile.Release is there any compiling problem?
|
|
|
As I know, the wallet must run on the same server of the blockchain so that the blockchain can rpc call to the wallet and get the data, is there any way that I can put wallet and blockchain on different server? I tried the conf of the wallet: server=1 listen=1 daemon=1 rpcuser=username rpcpassword=password rpcallowip=*.*.*.* rpcport=3910 port=3919 addnode=173.44.63.199
and I put php blockchain on another server, but it cannot connect.
|
|
|
This is a new topic if I saw the source code of a coin, how can I know which algorithm it use so that I can select the miner? How can I know the algorithm is X11 X13 or x15 or bitcoin sha256 etc? from the miner.cpp or ? Thanks
|
|
|
if i have source code, how can I know the algorithm for pow period so that I can select the miner? After the pow, during pos period, I do not need to mine, correct?
|
|
|
Any idea? This will also be the same for pos?
|
|
|
why this hppen? I use X11+POS ERROR: AcceptBlock() : reject proof-of-stake at height 85 ERROR: ProcessBlock() : AcceptBlock FAILED ERROR: CheckStake() : ProcessBlock, block not accepted
the POW accepted and POS rejected, so I think POW works but in the same time POS shows this error.
Thanks
|
|
|
Thanks After I pow to mine all the blocks, then pure pos, during this period I can just keep getting one new block every min age?
|
|
|
thanks for help, thinking about: min age: 1 hour, so a wallet will keep sync at most 1 hour max age=-1, no limitation each year: 3-5% supply: not sure yet, think something like 10500000
POW: 10 blocks(X11), and then POS
I am also thinking in POS period, I should still mine or not, just keep the wallet open?
|
|
|
thank I think blockchain must add new block to fix "out of sync" problem. When I start wallet, it always shows "out of sync", the wallet start to sync only after a new block added to the chain. In order to add a new chain, a new transaction must happen such as a new block mined. So before the new interest generated, no new block will be generated. The new interest only be generated after the min age, for example, the min_age is 3 hours, after 3 hours, new interest generated, and a new block can be created based on this new interest, and a new block added to the blockchain, and the "out of sync" wallet can keep sync because the new block added to the chain. in the future, every 3 hours(min age), some interest generated, and a new block generated, and added to the blockchain, and the "out of sync" wallets keep sync, is this correct? Thanks
|
|
|
|