Pages:
Author

Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 100. (Read 388610 times)

legendary
Activity: 1330
Merit: 1000
Blockchain Developer
MY wallet doesn't seem to be staking either.  I haven't had it open 24/7 but I have high coin weight and have kept it open for several hours at a time. Will try troulbe shooting it soon.
hero member
Activity: 526
Merit: 500
Its all about the Gold
i just realized i have some debug log file errors as well and they sorta match flungspun.

pool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input

and it goes for about another hour then just stops

  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  getblocks 499044 to 00000000000000000000 limit 500
    getblocks stopping at limit 499543 0000000003aa8f3c15f2
  Flush(false)
  blkindex.dat refcount=0
  blkindex.dat checkpoint
  ThreadSocketHandler exited
  blkindex.dat closed
  DBFlush(false) ended              64ms
  StopNode()
  ThreadMessageHandler exited
  ipcThread exited
  ThreadStakeMinter exiting, 0 threads remaining
  Flushed 757 addresses to peers.dat  52ms
  Flush(true)
  DBFlush(true) ended               0ms
  BottleCaps exited

   trying connection 46.109.153.185 lastseen=18.4hrs
  ERROR: ConnectInputs() : 4e61361746 prev tx already used at (nFile=1, nBlockPos=249619284,

nTxPos=249620326)
  ERROR: CTxMemPool::accept() : ConnectInputs failed 4e61361746
  ERROR: FetchInputs() : 60f3a93cdc mempool Tx prev not found c03c31f9d8
  stored orphan tx 60f3a93cdc (mapsz 2)
  ERROR: FetchInputs() : 20bbb12c2e mempool Tx prev not found c03c31f9d8
  stored orphan tx 20bbb12c2e (mapsz 3)
  ERROR: FetchInputs() : 4a17a5c925 mempool Tx prev not found 20bbb12c2e
  stored orphan tx 4a17a5c925 (mapsz 4)
  ERROR: FetchInputs() : f59acbd41a mempool Tx prev not found 537621253e
  stored orphan tx f59acbd41a (mapsz 5)
  ERROR: FetchInputs() : 3164984db9 mempool Tx prev not found f59acbd41a
  stored orphan tx 3164984db9 (mapsz 6)
  ERROR: FetchInputs() : 5b1caca8aa mempool Tx prev not found 24d86e78d1
  stored orphan tx 5b1caca8aa (mapsz 7)
  ERROR: FetchInputs() : 9e382d5db4 mempool Tx prev not found 8b0df54723
  stored orphan tx 9e382d5db4 (mapsz Cool
  ERROR: FetchInputs() : eadd5c09c9 mempool Tx prev not found 9fee54b6ef
  stored orphan tx eadd5c09c9 (mapsz 9)
  ERROR: FetchInputs() : da6a00b227 mempool Tx prev not found 4a17a5c925
  stored orphan tx da6a00b227 (mapsz 10)
  ERROR: FetchInputs() : 9604c57442 mempool Tx prev not found 3164984db9
  stored orphan tx 9604c57442 (mapsz 11)
  ERROR: FetchInputs() : 05aff6125f mempool Tx prev not found 5b1caca8aa
  stored orphan tx 05aff6125f (mapsz 12)
  ERROR: FetchInputs() : 8626a0888c mempool Tx prev not found db26b06965
  stored orphan tx 8626a0888c (mapsz 13)
  ERROR: FetchInputs() : 4c888e5f28 mempool Tx prev not found c086f9a6c6
  ignoring large orphan tx (size: 6960, hash: 4c888e5f28)
  ERROR: FetchInputs() : a4a1604842 mempool Tx prev not found 7f52ac49ab
  stored orphan tx a4a1604842 (mapsz 14)
  ERROR: FetchInputs() : cf8ec956dc mempool Tx prev not found 05aff6125f
  stored orphan tx cf8ec956dc (mapsz 15)
  ERROR: FetchInputs() : dd74f4aa60 mempool Tx prev not found bee12baeef
  stored orphan tx dd74f4aa60 (mapsz 16)
  ERROR: FetchInputs() : 27c2491d83 mempool Tx prev not found 5368b43c48
  stored orphan tx 27c2491d83 (mapsz 17)
  ERROR: FetchInputs() : ff5436dc40 mempool Tx prev not found c7d695b33e
  stored orphan tx ff5436dc40 (mapsz 18)
  ERROR: FetchInputs() : 00b606f8cf mempool Tx prev not found a4a1604842
  stored orphan tx 00b606f8cf (mapsz 19)
  ERROR: FetchInputs() : 319fae4a4e mempool Tx prev not found da6a00b227
  stored orphan tx 319fae4a4e (mapsz 20)
  ERROR: FetchInputs() : 62913ae613 mempool Tx prev not found ff5436dc40
  stored orphan tx 62913ae613 (mapsz 21)
  ERROR: FetchInputs() : a50b6dc66b mempool Tx prev not found 62913ae613
  stored orphan tx a50b6dc66b (mapsz 22)
  ERROR: FetchInputs() : 6b3e79b992 mempool Tx prev not found 27c2491d83
  stored orphan tx 6b3e79b992 (mapsz 23)
  ERROR: FetchInputs() : 2081766ac6 mempool Tx prev not found 6b3e79b992
  stored orphan tx 2081766ac6 (mapsz 24)
  ERROR: FetchInputs() : 7b11aa44c9 mempool Tx prev not found a50b6dc66b
  stored orphan tx 7b11aa44c9 (mapsz 25)
  ERROR: FetchInputs() : 0955c0f5e0 mempool Tx prev not found 97da421459
  stored orphan tx 0955c0f5e0 (mapsz 26)
  ERROR: FetchInputs() : 660183c220 mempool Tx prev not found 0955c0f5e0
  stored orphan tx 660183c220 (mapsz 27)
  ERROR: FetchInputs() : 599458ce8a mempool Tx prev not found 00b606f8cf
  stored orphan tx 599458ce8a (mapsz 28)
  ERROR: FetchInputs() : fd6d426504 mempool Tx prev not found 2081766ac6
  stored orphan tx fd6d426504 (mapsz 29)
  ERROR: FetchInputs() : 4c3a97395a mempool Tx prev not found 660183c220
  stored orphan tx 4c3a97395a (mapsz 30)
  ERROR: FetchInputs() : 91546af45f mempool Tx prev not found 4c3a97395a
  stored orphan tx 91546af45f (mapsz 31)
  ERROR: FetchInputs() : ecd8619d12 mempool Tx prev not found bdaaa9d201
  stored orphan tx ecd8619d12 (mapsz 32)
  ERROR: FetchInputs() : 88493a2007 mempool Tx prev not found 112fea726b
  stored orphan tx 88493a2007 (mapsz 33)
  ERROR: FetchInputs() : 7a971e9d5c mempool Tx prev not found 88493a2007
  stored orphan tx 7a971e9d5c (mapsz 34)
  ERROR: FetchInputs() : 2bd442beef mempool Tx prev not found ecd8619d12
  stored orphan tx 2bd442beef (mapsz 35)
  ERROR: FetchInputs() : 665339fd16 mempool Tx prev not found 8819acc3b5
  stored orphan tx 665339fd16 (mapsz 36)
  ERROR: FetchInputs() : dfe715eb10 mempool Tx prev not found fd6d426504
  stored orphan tx dfe715eb10 (mapsz 37)
  ERROR: FetchInputs() : 04c57a6111 mempool Tx prev not found 2bd442beef
  stored orphan tx 04c57a6111 (mapsz 38)
  ERROR: FetchInputs() : 0805323daa mempool Tx prev not found 7a971e9d5c
  stored orphan tx 0805323daa (mapsz 39)
  ERROR: FetchInputs() : 1590c1c951 mempool Tx prev not found 665339fd16

then this started and all looks good again:

  ERROR: FetchInputs() : c1db77e899 mempool Tx prev not found 72f9437c90
  ignoring large orphan tx (size: 10576, hash: c1db77e899)
  ERROR: FetchInputs() : bcd683b85f mempool Tx prev not found 1fa5315cb8
  stored orphan tx bcd683b85f (mapsz 1005)
  ERROR: FetchInputs() : 41c0466ffa mempool Tx prev not found 63818df17a
  stored orphan tx 41c0466ffa (mapsz 1006)
  ERROR: ConnectInputs() : 4022ed06df prev tx already used at (nFile=1, nBlockPos=239824244,

nTxPos=239824402)
  ERROR: CTxMemPool::accept() : ConnectInputs failed 4022ed06df
  ERROR: ConnectInputs() : 99be4a80ce prev tx already used at (nFile=1, nBlockPos=235147347,

nTxPos=235147686)
  ERROR: CTxMemPool::accept() : ConnectInputs failed 99be4a80ce
  trying connection 86.128.154.85 lastseen=71.4hrs
  connection timeout
  trying connection 210.55.212.85 lastseen=13.8hrs


any idea what this means? good? bad?


EDit: i have been getting staking and on latest 2.1
sr. member
Activity: 414
Merit: 251
Can't see anything wrong, or is there?
I renamed the exe to get windows firewall to go back through the unblock dialogue again
re-downloaded the blockchain with the 2.1 version
copied the lot onto a win7 laptop - no joy
all test machines have one or more active qts either receiving coin or stake or both for various coins
vista win7 and 8.1

*Edit* also no tried exporting the private key into a new wallet and doing a rescan ... same situation
and looking at my address in the explorer there seems to be 0.000391 Cap unexplained in the balance Huh

Well you have done everything that I would have tried.  You can try using the following start up switches. This will cause the debug.log to grow quickly but could pinpoint the issue.  -debug -printcreation -printcoinstake -printcoinage

Otherwise at this point I would need to run specific debug statements using your wallet or the key.  But just looking at my wallet, my friends wallet and the block explorer, all staking is working as far as I can tell. So I can't figure out what would be preventing your coins from staking.
Right then - glad it's a problem that needs solving rather than obvious user error

Doing as suggested now. plenty new data in the debug
Only thing that jumps out at me is this

Code:
ERROR: FetchInputs() : 8112982c6c mempool Tx prev not found 419047a3b9
07/05/14 18:07:47 stored orphan tx 8112982c6c (mapsz 1)
07/05/14 18:07:47 received: tx (980 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : ee69343d01 mempool Tx prev not found 89da628efd
07/05/14 18:07:47 stored orphan tx ee69343d01 (mapsz 2)
07/05/14 18:07:47 received: tx (197 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : 1c449b4d8d mempool Tx prev not found 4778585c6e
07/05/14 18:07:47 stored orphan tx 1c449b4d8d (mapsz 3)
07/05/14 18:07:47 received: tx (230 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : f1b158c245 mempool Tx prev not found 1c449b4d8d
07/05/14 18:07:47 stored orphan tx f1b158c245 (mapsz 4)
07/05/14 18:07:47 received: tx (229 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : a3423d06ed mempool Tx prev not found f1b158c245
07/05/14 18:07:47 stored orphan tx a3423d06ed (mapsz 5)
07/05/14 18:07:47 received: tx (231 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : 9635f5d360 mempool Tx prev not found a3423d06ed
07/05/14 18:07:47 stored orphan tx 9635f5d360 (mapsz 6)
07/05/14 18:07:47 received: tx (982 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : 053bc93ab3 mempool Tx prev not found 9635f5d360
07/05/14 18:07:47 stored orphan tx 053bc93ab3 (mapsz 7)
07/05/14 18:07:47 received: tx (197 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : b8c7e3abbb mempool Tx prev not found d2abe227b8
07/05/14 18:07:47 stored orphan tx b8c7e3abbb (mapsz 8)
07/05/14 18:07:47 received: tx (196 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : 9b87028ed4 mempool Tx prev not found 5c12fda005
07/05/14 18:07:47 stored orphan tx 9b87028ed4 (mapsz 9)
07/05/14 18:07:47 received: tx (230 bytes)
07/05/14 18:07:47 ERROR: FetchInputs() : 1ddc77fe10 mempool Tx prev not found 9b87028ed4
07/05/14 18:07:47 stored orphan tx 1ddc77fe10 (mapsz 10)

amongst much I don't understand

How much do you want to see of the debug?
Attach a PM?

Happy to send you secure wallet data if it come to that.

sr. member
Activity: 504
Merit: 254
One little Coin Control bug I noticed today while cleaning up some dust.  Using 2.1 version.

On ~1/3 of the sends I was doing the calculated send fee was not correct.  Sometimes it was more sometimes it was less (ie coin control calculate fee to be 0.01 but upon sending it claims fee will be 0.011, another calculated fee at 0.006 but on sending it was only 0.004.)

Pretty minor bug but the underestimate causes the send to fail as your total to send becomes less than the value+fee.

I don't think it's a bug, more a lack of better solution. Coin control will give you an estimate of the fees no the actual fees.  I find that the more blocks you have selected, the farther away you will be from reality.

I didn't look into the code for this. But I know fees can be estimated like this

Code:
tx_size =  (inputs * 148) + (outputs * 34) + 10 ± "# inputs"

so I guess that plus and minus inputs argument could throw off the estimation the more inputs you have selected.

Maybe a better estimation equation could be used. I never found one.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Can't see anything wrong, or is there?
I renamed the exe to get windows firewall to go back through the unblock dialogue again
re-downloaded the blockchain with the 2.1 version
copied the lot onto a win7 laptop - no joy
all test machines have one or more active qts either receiving coin or stake or both for various coins
vista win7 and 8.1

*Edit* also no tried exporting the private key into a new wallet and doing a rescan ... same situation
and looking at my address in the explorer there seems to be 0.000391 Cap unexplained in the balance Huh

Well you have done everything that I would have tried.  You can try using the following start up switches. This will cause the debug.log to grow quickly but could pinpoint the issue.  -debug -printcreation -printcoinstake -printcoinage

Otherwise at this point I would need to run specific debug statements using your wallet or the key.  But just looking at my wallet, my friends wallet and the block explorer, all staking is working as far as I can tell. So I can't figure out what would be preventing your coins from staking.
sr. member
Activity: 274
Merit: 250
I'm trying to get CAPS from Cryptsy to my wallet to start xtra stakes.
Anyone know when their wallet will be not "Offline"Huh
legendary
Activity: 912
Merit: 1000
One little Coin Control bug I noticed today while cleaning up some dust.  Using 2.1 version.

On ~1/3 of the sends I was doing the calculated send fee was not correct.  Sometimes it was more sometimes it was less (ie coin control calculate fee to be 0.01 but upon sending it claims fee will be 0.011, another calculated fee at 0.006 but on sending it was only 0.004.)

Pretty minor bug but the underestimate causes the send to fail as your total to send becomes less than the value+fee.
sr. member
Activity: 414
Merit: 251
mine has been saying staking 50% chance within 1 hour for over 12 hours now.

I am on 2.1 do i need to redownload the blockchain to be on the right fork.

My apologize if i missed something.
As I understand
If you are on 2.1 and your block count agrees with http://cap.cryptocoinexplorer.com/
it's just a matter of waiting for the post fork dust to settle.
We seem to be steadily getting closer to 200% annual POS from 170ish yesterday.

Correct. I assume you got your stakes going good then FlungSpun..
Actually, no!
but I achieving enlightenment via patient application of zazen - calm body and mind

I'll post when a block stakes or my calm cracks Cheesy

If you have that must weight, it should stake right away.  Only the wrong version(2.0(double check getinfo)) or a locked wallet would cause the coins not to stake.  All of my 10k blocks, downloaded early May, staked right away. I even just got a block on my 7 coin set.

Keep an eye on the debug.log, it might have some clues if something is amiss.

Can't see anything wrong, or is there?
I renamed the exe to get windows firewall to go back through the unblock dialogue again
re-downloaded the blockchain with the 2.1 version
copied the lot onto a win7 laptop - no joy
all test machines have one or more active qts either receiving coin or stake or both for various coins
vista win7 and 8.1

*Edit* also no tried exporting the private key into a new wallet and doing a rescan ... same situation
and looking at my address in the explorer there seems to be 0.000391 Cap unexplained in the balance Huh


v2.1.0.0-g9409ca8-Caps2.0

Code:
{
"version" : "v2.1.0.0-g9409ca8-Caps2.0",
"protocolversion" : 70004,
"walletversion" : 60000,
}

Code:
07/05/14 15:36:18 trying connection 192.241.233.70:7685 lastseen=0.6hrs
07/05/14 15:36:18 connected 192.241.233.70:7685
07/05/14 15:36:18 send version message: version 70004, blocks=526374, us=86.161.0.8:7685, them=192.241.233.70:7685, peer=192.241.233.70:7685
07/05/14 15:36:19 Added time data, samples 12, offset -1 (+0 minutes)
07/05/14 15:36:19 receive version message: version 70004, blocks=526374, us=86.161.0.8:51860, them=192.241.233.70:7685, peer=192.241.233.70:7685
07/05/14 15:36:19 trying connection 65.186.210.229:7685 lastseen=2.6hrs
07/05/14 15:36:20 getblocks 515072 to 00000000000000000000 limit 500
07/05/14 15:36:20   getblocks stopping at limit 515571 0000000002935af9d7c6
07/05/14 15:36:21 getblocks 491072 to 00000000000000000000 limit 500
07/05/14 15:36:21   getblocks stopping at limit 491571 00000000124cc6fdb244
07/05/14 15:36:23 getblocks 502572 to 00000000000000000000 limit 500
07/05/14 15:36:23   getblocks stopping at limit 503071 000000000231866f3c2b
07/05/14 15:36:24 connection timeout
07/05/14 15:36:24 trying connection [2a01:4f8:150:8185::2]:7685 lastseen=20.7hrs
07/05/14 15:36:28 getblocks 515572 to 00000000000000000000 limit 500
07/05/14 15:36:28   getblocks stopping at limit 516071 0000000001c23184fa2e
07/05/14 15:36:29 getblocks 503072 to 00000000000000000000 limit 500
07/05/14 15:36:29   getblocks stopping at limit 503571 0000000001ddc4062242
07/05/14 15:36:29 getblocks 491572 to 00000000000000000000 limit 500
07/05/14 15:36:29   getblocks stopping at limit 492071 000000001b63b38e7cc2
07/05/14 15:36:29 connection timeout
07/05/14 15:36:30 trying connection 72.202.128.75:7685 lastseen=19.5hrs
07/05/14 15:36:35 getblocks 503572 to 00000000000000000000 limit 500
07/05/14 15:36:35   getblocks stopping at limit 504071 0000000013beaed0e999
07/05/14 15:36:35 connection timeout
07/05/14 15:36:35 trying connection 81.164.85.197:7685 lastseen=12.6hrs
07/05/14 15:36:36 getblocks 486072 to e7d99be52758944e65f6 limit 500
07/05/14 15:36:36   getblocks stopping at limit 486571 000000000a4017c3ad71
07/05/14 15:36:37 getblocks 492072 to 00000000000000000000 limit 500
07/05/14 15:36:37   getblocks stopping at limit 492571 0000000020b13db8cca5
07/05/14 15:36:40 connection timeout
07/05/14 15:36:41 trying connection [2a02:c200:1:10::2360:1]:7685 lastseen=34.1hrs
07/05/14 15:36:42 getblocks 504072 to 00000000000000000000 limit 500
07/05/14 15:36:42   getblocks stopping at limit 504571 000000001ab2dc95cdfa
07/05/14 15:36:44 getblocks 486572 to 00000000000000000000 limit 500
07/05/14 15:36:44   getblocks stopping at limit 487071 0000000024af28f94dcf
07/05/14 15:36:44 getblocks 492572 to 00000000000000000000 limit 500
07/05/14 15:36:44   getblocks stopping at limit 493071 000000003853c6a98e72
07/05/14 15:36:46 connection timeout

sr. member
Activity: 274
Merit: 250
Got a stake on my ~360CAP block early after starting to stake.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
mine has been saying staking 50% chance within 1 hour for over 12 hours now.

I am on 2.1 do i need to redownload the blockchain to be on the right fork.

My apologize if i missed something.
As I understand
If you are on 2.1 and your block count agrees with http://cap.cryptocoinexplorer.com/
it's just a matter of waiting for the post fork dust to settle.
We seem to be steadily getting closer to 200% annual POS from 170ish yesterday.

Correct. I assume you got your stakes going good then FlungSpun..
Actually, no!
but I achieving enlightenment via patient application of zazen - calm body and mind

I'll post when a block stakes or my calm cracks Cheesy

If you have that must weight, it should stake right away.  Only the wrong version(2.0(double check getinfo)) or a locked wallet would cause the coins not to stake.  All of my 10k blocks, downloaded early May, staked right away. I even just got a block on my 7 coin set.

Keep an eye on the debug.log, it might have some clues if something is amiss.
sr. member
Activity: 414
Merit: 251
mine has been saying staking 50% chance within 1 hour for over 12 hours now.

I am on 2.1 do i need to redownload the blockchain to be on the right fork.

My apologize if i missed something.
As I understand
If you are on 2.1 and your block count agrees with http://cap.cryptocoinexplorer.com/
it's just a matter of waiting for the post fork dust to settle.
We seem to be steadily getting closer to 200% annual POS from 170ish yesterday.

Correct. I assume you got your stakes going good then FlungSpun..
Actually, no!
but I achieving enlightenment via patient application of zazen - calm body and mind

I'll post when a block stakes or my calm cracks Cheesy
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
mine has been saying staking 50% chance within 1 hour for over 12 hours now.

I am on 2.1 do i need to redownload the blockchain to be on the right fork.

My apologize if i missed something.
As I understand
If you are on 2.1 and your block count agrees with http://cap.cryptocoinexplorer.com/
it's just a matter of waiting for the post fork dust to settle.
We seem to be steadily getting closer to 200% annual POS from 170ish yesterday.

Correct. I assume you got your stakes going good then FlungSpun..
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Getting mismatched coin errors now, already spent, that kind of stuff. Repairwallet brings em back, but is there any way to know how many of the coins in the wallet are actually spendable now?

I would first try to restart client with -rescan. 

A more aggressive approach is to use -salvagewallet. Salvage Wallet will also remove your addresses. So be sure to export them if you need them.


There is a another rpc command -zapwallettxs but that is not in your version of CAP. If neither of the above approaches work, let me know.
Ok, so after trying to send out some coins, I got the mismatched / spent error again. Tried salvagewallet, now it can't initialize the keypool and crashes.

Do you have a backup? I have one more thing to try.

Create a new dir c:\cap_test put the good wallet.dat there.
 Start the client with these switches.

-datadir=c:\cap_test and -listen=0 (only if you are still running the other version)

Let that one re download the block chain and see if that works.  If not, please send me a PM.
legendary
Activity: 3486
Merit: 1126

Hey guys! I've moved CAP off this pool and into my new DRK paying Multipool.  Would love some more testers as I've got no fee's during this period. Here are the details:

xpool - DRK Multipool

 
PROP reward system
Scrypt & SHA256 & X11 Algo's
DDoS Protected
High Performance Backend
Simple setup and usage
0% Fees while in BETA
To mine:
Cheers and Happy Hashing!

Our wallets are up-to-date FYI.
sr. member
Activity: 414
Merit: 251
mine has been saying staking 50% chance within 1 hour for over 12 hours now.

I am on 2.1 do i need to redownload the blockchain to be on the right fork.

My apologize if i missed something.
As I understand
If you are on 2.1 and your block count agrees with http://cap.cryptocoinexplorer.com/
it's just a matter of waiting for the post fork dust to settle.
We seem to be steadily getting closer to 200% annual POS from 170ish yesterday.
legendary
Activity: 1148
Merit: 1000
mine has been saying staking 50% chance within 1 hour for over 12 hours now.

I am on 2.1 do i need to redownload the blockchain to be on the right fork.

My apologize if i missed something.
sr. member
Activity: 414
Merit: 251
Might have an issue over here.
One wallet with 4 blocks of 10k doesn't want to stake.



All day with no stake - 10+ hours. I know I'm unlucky sometimes but ..
Also note my weight is bigger than the network. I've seen this on HBN once or twice with big blocks staking

All four blocks should be over the 1k limit for stake by a fair margin as I was planning on moving funds but didn't this month.

When the earlier problems hit I switched machines and re-downloaded the chain, swapped out wallet on that and still no dice.....
but machines both agree with current block on http://cap.cryptocoinexplorer.com/

The network is just jammed full of blocks right now I would expect. I have known for a while that most clients network stake weight calculations aren't accurate, I have a high stake weight as well without any stakes yet. They will come I am sure, but at this point I think that luck is a major factor.

The good news is that PoS blocks are overwhelming the PoW blocks on the chain right now.  There is a big queue but it is being served quickly.

Well if it's just a case of waiting then fine.
I know the HBN client can be a little pessimistic on your 50% times so I was thinking it would be over in a flash.
coins won't be going anywhere so it only a case of loss of compound interest (the most powerful force in the universe!)
sr. member
Activity: 414
Merit: 251
Might have an issue over here.
One wallet with 4 blocks of 10k doesn't want to stake.



All day with no stake - 10+ hours. I know I'm unlucky sometimes but ..
Also note my weight is bigger than the network. I've seen this on HBN once or twice with big blocks staking

All four blocks should be over the 1k limit for stake by a fair margin as I was planning on moving funds but didn't this month.

When the earlier problems hit I switched machines and re-downloaded the chain, swapped out wallet on that and still no dice.....
but machines both agree with current block on http://cap.cryptocoinexplorer.com/

Please make sure you are using 2.1 Version 2.0 had an issue with large stakes.

https://github.com/Tranz5/bottlecaps/releases


Yes I'm on 2.1 now but I was on v2 until about 5-10 mins after the fork.

I left this all night so now its been 24 hours without stake - still get a 6 minute 50% :/

newbie
Activity: 57
Merit: 0
Getting mismatched coin errors now, already spent, that kind of stuff. Repairwallet brings em back, but is there any way to know how many of the coins in the wallet are actually spendable now?

I would first try to restart client with -rescan. 

A more aggressive approach is to use -salvagewallet. Salvage Wallet will also remove your addresses. So be sure to export them if you need them.


There is a another rpc command -zapwallettxs but that is not in your version of CAP. If neither of the above approaches work, let me know.
Ok, so after trying to send out some coins, I got the mismatched / spent error again. Tried salvagewallet, now it can't initialize the keypool and crashes.
hero member
Activity: 658
Merit: 503
Monero Core Team
See above
Thanks.

Also, I wrote a "oneliner" for downloading and compiling CAP wallet and create a shortcut on your desktop, on Linux (tested with Manjaro)
Code:
mkdir ~/cryptos ; cd ~/cryptos && rm -rf bottlecaps && git clone https://github.com/bottlecaps-foundation/bottlecaps && cd bottlecaps && qmake-qt4 bottlecaps-qt.pro && make && ln -s ~/cryptos/bottlecaps/BottleCaps-qt ~/Desktop/CAP
Notes:
  • The mkdir ~/cryptos ; cd ~/cryptos && rm -rf bottlecaps is not necessary - I just prefer things tidy
  • ln -s ~/cryptos/bottlecaps/BottleCaps-qt ~/Desktop/CAP takes care of the shortcut; if you are not using an English Linux, change Desktop to how the desktop is names in your language.
Pages:
Jump to: