Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS

[jjj0923]

fyi: deposits to cryptsy appear to be broken.

[mineabit]

Bottlecaps pool now online running latest wallet: http://cap.pool.mineabit.com

Prop payment system, 2% fee and 0.001 tx fee

Payouts tested and working to Cryptsy

[jjj0923]

Bottlecaps pool now online running latest wallet: http://cap.pool.mineabit.com

Prop payment system, 2% fee and 0.001 tx fee

Payouts tested and working to Cryptsy

well - Ive got wallet v2.0.0.0 and my deposit to cryptsy is not working,.

I've got a support ticket open too and they sais they had to escalate the problem - so my experience is not the same as yours.

[ebeth08]

Bottlecaps pool now online running latest wallet: http://cap.pool.mineabit.com

Prop payment system, 2% fee and 0.001 tx fee

Payouts tested and working to Cryptsy

well - Ive got wallet v2.0.0.0 and my deposit to cryptsy is not working,.

I've got a support ticket open too and they sais they had to escalate the problem - so my experience is not the same as yours.

Same problem here.  Deposit to Craptsy never went through.  Opened ticket, hope they figure it out soon.  Trying mineabit pool, will post how it goes.  2% fee is high for this coin though.  Most pools at 0%.  Maybe try 1% to get some hash??

[jjj0923]

Bottlecaps pool now online running latest wallet: http://cap.pool.mineabit.com

Prop payment system, 2% fee and 0.001 tx fee

Payouts tested and working to Cryptsy

well - Ive got wallet v2.0.0.0 and my deposit to cryptsy is not working,.

I've got a support ticket open too and they sais they had to escalate the problem - so my experience is not the same as yours.

Same problem here.  Deposit to Craptsy never went through.  Opened ticket, hope they figure it out soon.  Trying mineabit pool, will post how it goes.  2% fee is high for this coin though.  Most pools at 0%.  Maybe try 1% to get some hash??

I contacted the pool operator where I mine (cryptotroll) and he told me they often takes down their wallets to save resources and only start them once a day or so to process deposits

[presstab]

Bottlecaps pool now online running latest wallet: http://cap.pool.mineabit.com

Prop payment system, 2% fee and 0.001 tx fee

Payouts tested and working to Cryptsy

well - Ive got wallet v2.0.0.0 and my deposit to cryptsy is not working,.

I've got a support ticket open too and they sais they had to escalate the problem - so my experience is not the same as yours.

This could easily be cryptsy updating their coin daemon in anticipation of the fork. Rescan can take a long time depending on what equipment they have running. I would not be the least bit worried. Once the daemon catches up you will/should see your coins come through. I have seen this happen a few times with different coins on cryptsy. What is important to remember is that cryptsy has a hot wallet for deposits/withdrawal and cold wallet for reserves. From what I have experienced, trading coins has nothing to do with either wallet and is just part of cryptsy's internal accounting platform rather than a physical address change of coins.

So as long as cryptsy successfully updates the daemon to be up to date, everything will eventually come through. So sit back, relax and continue to whale watch in the mean time.

[jjj0923]

Bottlecaps pool now online running latest wallet: http://cap.pool.mineabit.com

Prop payment system, 2% fee and 0.001 tx fee

Payouts tested and working to Cryptsy

well - Ive got wallet v2.0.0.0 and my deposit to cryptsy is not working,.

I've got a support ticket open too and they sais they had to escalate the problem - so my experience is not the same as yours.

This could easily be cryptsy updating their coin daemon in anticipation of the fork. Rescan can take a long time depending on what equipment they have running. I would not be the least bit worried. Once the daemon catches up you will/should see your coins come through. I have seen this happen a few times with different coins on cryptsy. What is important to remember is that cryptsy has a hot wallet for deposits/withdrawal and cold wallet for reserves. From what I have experienced, trading coins has nothing to do with either wallet and is just part of cryptsy's internal accounting platform rather than a physical address change of coins.

So as long as cryptsy successfully updates the daemon to be up to date, everything will eventually come through. So sit back, relax and continue to whale watch in the mean time.

THANKS

[mineabit]

suggestion received and fee reduced to 1%!

[mineabit]

To go back to the Cryptsy issue, it seems to be a problem on their side. Deposits worked fine yesterday but now i see the transactions going over but the accounts are not credited.

On that note, if they are updating the wallet they might have issues downloading the blockchain as i found it took me over 4 hours 2 days ago.


EDIT: Just received my last block payout to Cryptsy.

[ymod123]

is the wallet staking? since may 28 my wallet havent stake yet

[presstab]

is the wallet staking? since may 28 my wallet havent stake yet

What size of blocks do you have and how old?

[NuShrike]

is the wallet staking? since may 28 my wallet havent stake yet

How old is your oldest coin?

I'm staking with my 5/13 coin.

Meantime, what's wrong with the difficulty? It's adjusting up so slowly when it used to easily hit 8.x+ when cryptotroll was over 100Mhs.  Today, cryptotroll hit over 200Mhs and difficulty stayed around 3, and only barely hitting 5 now.

[crackfoo]

Come get your CAP!



http://www.hasher.ca

PROP reward system
Worker Stats
DDoS Protected
High Performance Backend
Simple setup and usage
Auto ProfitSwitching Ports (beta testing now)

To mine:

Username: your CAP wallet address OR a generated Global Key
Password: anything
URL (vardiff): stratum+tcp://stratum.hasher.ca:3634

CAP go straight to your wallet once the block is confirmed. We don't hold your CAP!

Cheers and Happy Hashing!

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

xpool - BTC Multipool

 

http://www.xpool.ca

PROP reward system

Scrypt & SHA256 Algo's

DDoS Protected

High Performance Backend

Simple setup and usage

0% Fees while in BETA

To mine:

http://www.xpool.ca/get_started

Cheers and Happy Hashing!

[ebeth08]

The coins I sent Crypsty have been stuck for over 2 days now.  DEV, please touch base with Crypsty and fix this wallet issue.  This issue needs to be resolved ASAP.  This is VERY frustrating, ready to walk away from this nightmare soon.

[Hilux74]

The coins I sent Crypsty have been stuck for over 2 days now.  DEV, please touch base with Crypsty and fix this wallet issue.  This issue needs to be resolved ASAP.  This is VERY frustrating, ready to walk away from this nightmare coin soon.

More details.  Was what you sent made up of lots of tiny incoming amounts? 

Most times when sends get stuck with 0 confirms in any coin it is the dust/large transaction error.  Opening your wallet with the -salvagewallet command should recover the CAPs back to your wallet and then try sending in smaller amounts.  It seems to me the error occurs when send amount > (ave incoming amounts X 64), ie if incoming pool payments were 1 XYZ, then you can send 64 XYZ without issue.

*I have not had this issue with a POS coin yet so I don't know if tiny POS block rewards contribute to the issue.  I assume they do so with HBN I tend to recombine most blocks using coin control and send to an alternate wallet to avoid eventual tiny blocks and tiny POS rewards.  Now that CAPs has coin control it can managed the same way.

[ebeth08]

The coins I sent Crypsty have been stuck for over 2 days now.  DEV, please touch base with Crypsty and fix this wallet issue.  This issue needs to be resolved ASAP.  This is VERY frustrating, ready to walk away from this nightmare coin soon.

More details.  Was what you sent made up of lots of tiny incoming amounts? 

Most times when sends get stuck with 0 confirms in any coin it is the dust/large transaction error.  Opening your wallet with the -salvagewallet command should recover the CAPs back to your wallet and then try sending in smaller amounts.  It seems to me the error occurs when send amount > (ave incoming amounts X 64), ie if incoming pool payments were 1 XYZ, then you can send 64 XYZ without issue.

*I have not had this issue with a POS coin yet so I don't know if tiny POS block rewards contribute to the issue.  I assume they do so with HBN I tend to recombine most blocks using coin control and send to an alternate wallet to avoid eventual tiny blocks and tiny POS rewards.  Now that CAPs has coin control it can managed the same way.

According to my wallet, Status: 1347 confirmations, broadcast through 8 nodes
The problem is with Crypsty.  I don't believe the DEV ever contacted them to upgrade their wallet.  All Crypsty has told me for the last 2 days is they are working on it.

[NuShrike]

The problem is with Crypsty.  I don't believe the DEV ever contacted them to upgrade their wallet.  All Crypsty has told me for the last 2 days is they are working on it.

There should be no need for Cryptsy to update their wallet before the hard-fork. The protocol didn't change, just the wallet.

However, Cryptsy has been quite unreliable moving CAP in. I've had 2 week-long ticket open a few weeks ago (before these wallet changes) because they couldn't figure out what was going on with their deposits.  Happening again.

[ebeth08]

The problem is with Crypsty.  I don't believe the DEV ever contacted them to upgrade their wallet.  All Crypsty has told me for the last 2 days is they are working on it.

There should be no need for Cryptsy to update their wallet before the hard-fork. The protocol didn't change, just the wallet.

However, Cryptsy has been quite unreliable moving CAP in. I've had 2 week-long ticket open a few weeks ago (before these wallet changes) because they couldn't figure out what was going on with their deposits.  Happening again.

Doesn't make any sense.  But if this has been going on for weeks, I am def out.  There's only 1 exchange for this coin, not worth the headaches.

[presstab]

The problem is with Crypsty.  I don't believe the DEV ever contacted them to upgrade their wallet.  All Crypsty has told me for the last 2 days is they are working on it.

There should be no need for Cryptsy to update their wallet before the hard-fork. The protocol didn't change, just the wallet.

However, Cryptsy has been quite unreliable moving CAP in. I've had 2 week-long ticket open a few weeks ago (before these wallet changes) because they couldn't figure out what was going on with their deposits.  Happening again.

Doesn't make any sense.  But if this has been going on for weeks, I am def out.  There's only 1 exchange for this coin, not worth the headaches.

The coin has not forked yet, so blaming any problems with cryptsy on a fork isn't logical. Get in contact with cryptsy, they probably need to rescan the block chain. Send them the tx id.

Tranz is on vacation and warned us all that he won't be on the internet for a little while. Go ahead and feel free to contact cryptsy yourself. There are several high level cryptsy people that monitor this thread, and I am guessing that they have already updated their daemon anyways.

Others have posted that their transactions went through.  Maybe if you want another exchange, then submit it for voting on a different exchange and then announce it here so that we can all vote there.  I know allcoin.com has voting.

[Hilux74]

Cryptsy has issues from time to time but you should be ranting in a Cryptsy thread not in the CAPs thread...