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

That is too funny...

Video-cards (The 7970's), went from selling for $250-$300 NEW, back up to $400-$600 USED since all the alt-coins started rising again. (Good for us, because that keeps the cost of production up. Real good for Radeon, because this has got to be one of the only cards that goes back UP in price, every year... As opposed to going down by half each year. lol.)

Back up and running with 8 connections. The one with 3 was running near-zero diff, and taller, but obviously the wrong height, by majority.

Block-crawler still not responding, so I assume it is on the same bad chain.

Block-height is  219226 and diff shows as 27.3K in the miners. (~0.41656494140625 diff)

CAUTION: Fork?

Found my computers down and CAP wallet out of sync with only 3 connections this morning. Block-crawler down too... Reloading an old backup of the chain, since the existing chain isn't fixing itself, still... (Didn't realize that was still an issue.)

Hope it finds the right connections!

P.P.P.S. That needs to be fixed too... Chain correction. Whatever it tried to do, just caused my PC to shutdown and, again, I am having to download the whole chain or resort to my backup of a chain. (A backup I have to do manually, because the program doesn't auto-backup from the last hard-coded block.)

Mullick, any thoughts about the rebranding suggestions?
- My final suggestion is just "CAP" or "CAPs"... Thus, just calling them "Caps", or "Digital-Caps", or "Crypto-Caps", or "Cap-Coins"... as in, "Apex", or "Limit", or "Top". (Makes rebranding simple and easy. More like a refinement of the product. The wallet and site would not brand them as "digital-caps"... Just "CAP"... But they would be referred to as a "Digital Cap", or any of the above mentioned knick-names.)

Possibly too, some of the other suggestions, to make this next release a mile-stone release?
- Fixing the text for "what the fees actually go towards".
- Consideration for a flat-TXfee, since the penalty for unavoidable dust is irregular and makes no sense. (Similar to how POS is a fixed-percent. Since fees can be avoided entirely by inter-trading on the exchange anyways. Something like 0.01% to a minimum of 0.00000001, in order to be a valid TX. To limit super-micro dust-tx's, if it comes to that.)
- POS->POW(Idle) ability, for reducing low-diff mine-sell abuse. (And to reward those who save that mine POS, when diffs get low.)
- Every-other-block diff-adjust, instead of every-block adjustments. Limiting POS to the "other" blocks, when POS is available. (To alleviate network rejections where blocks just don't circulate fast enough, when POS waves happen.)
- Wallet-export and wallet-import, of only the critical "recreation" address info. (Not the individual tx's. For paper-wallet and safe-back-up.)

P.S. There is a lot to read... lol. (I just summed-up my crap into this one post.)

P.P.S. I am still buying all these under-priced CAPs, which are slowly rising in dollar-value, but not faster than I can buy them. (All those listing "sells" low are just handing me their investments. lol. The hardest part is buying them before the re-listing bot buys the lower ones. But he is still selling them to me at a bargain too! xD)

Was much is "excessive"? Do you have a log?

Got an interesting email from my hosting provider. The server which runs the checkpointing client was suspended due to "excessive" bandwith usage.

Leave my caps alone! Please and thank you

So I moved it to another IP address. If it happens again ill look into some form of protection. This poses no threat to the network. It is self sufficient now im moving the checkpointing depth down now as well reducing the "Dependence" on the server

Im back now sorry for the long absense Had a family emergency and was out of town got back for one day then left again. 2,200 Miles later Im back lol

Checkpointing server got hung up a while back I rebooted it remotely the other day checkpoint message should be gone. Ill finish up the wallet hopefully tonight.

Ill keep everyone posted throughout the night

Also a suggestion...

Why not make the wallet use some CPU use, when not POSing... To mine POW, while POW exists. (This way, any-time the diff is low, instead of it all going to only a few cash-out miners, the found coins go to the people POSing, who would welcome the nice 10-coin reward between POSing blocks. Thus, limiting the cash-out, which just degrades the overall value and lowers the diff by pushing away miners.)

Eg, it only POSes, when POS is available to be generated. However, when not POSing, it just sits idle. If you allow us to select %CPU use, we could dedicate spare cycles to help reduce the further under-selling from cash-outs. One that wouldn't interfere with our normal computer use, by using 100% cpu power.

Perfect time to test that theory... If it adds only 20Mhs from the POS open-wallets, that is less POW miners will get, and will have to demand more for their coins. Yet, it won't be so much power that it would cripple the network when more actual miners begin mining the coin again. But the more POS users, the harder it becomes to "solo-harvest" by degrading other miners from mining. Which is happening now. Was happening... But I can't keep buying everyone's coins forever! (Ok, I am buying many, not all of them. lol. The point is, I am not buying them then instantly re-listing them, stopping others from mining and making it go lower.)

At these prices, the coins are still a steal to buy. Not so great to sell though, unless you are mining for the future.

Anyone have the wallet/daemon running on a raspberry-pi?

EDIT: Found a site with a nice tutorial... going to try and see how this works for the daemon...
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/

Just have to put apachee with PHP and MySQL on there too... and you have a whole gateway sub-processor account all ready to go!

Would make a great turn-key solution, to sell, for those wanting processing integration on websites. (As opposed to bogging-down the website-server with that additional processing load, and exposing the wallet directly to the server. Especially since most web-shops are on shared-servers or home-servers.)

I would just rather spend $35 for a wallet-processor, instead of another $300+ for another dedicated power-hungry computer.

Plus, I can just put it right next to my router at home, where I can monitor it directly and swap-out physical wallets.

Now if the wallet just used something secure for talking, besides unsecured HTTP and JsonRPC... That would give us another advantage over other wallets. (Why it isn't HTTPS or simply encoded HTTP-URLs, I will never know.)

Also, might want to put up some simple RPC access-limits for the config. EG, I only need read-only access, or confirm-payment info. (As opposed to Allow-all, or Allow-none, by not allowing or not allowing RPC connections. Since the NAME and PASSWORD are both broadcast in the URL for POST connections over HTTP/HTTPS. Without URL encryption. EG, http://mywallet.com:3232/RPC?99s8f78ds7df8g7d9f8gdf6g7dsfsdfadfafdasd54656r5fg6" The command, name and pass would be encrypted, with salt, as well as the matching reply. Thus, useless reply to those without the key.)

Thus, having it limited to just those replies and commands, stops someone from maliciously "Creating new addresses", which would potentially break or fill a wallet with dead-addresses that can't be recovered through normal recreation of an earlier wallet. (That, or asking for wallet-info that otherwise might expose sensitive information or other commands from the wallet, from the JsonRPC interface, which I don't need. Which many of us will never even use. Those who do use them, also would know how to enable the ones they need. Thus, all except "Connection reply info", should be disabled, until turned-on in the config file.)

He said a few posts back, that he was indisposed for a brief moment. He was going to check-in from his laptop, from where-ever he was at... I am not sure how-much he will be able to do, away from home. Not like everyone keeps their programming artillery with them on the go!

I wish more people would chime-in, on the coin.

I am looking into the paper-wallet thing more. Since I will be making go-cards with it, like I did with min-coins, months ago. (Which is why I had that code in the first-place.)

Now if they just had a wallet-generator that was repeatable, based off the locking-password and the original first receive-address... That would give our wallets something that others don't have... Recreatable wallets, from two solid values. (Unlike now, where only the first 100 addresses are recreatable, and any beyond 100, are just lost, if you don't know them or the wallet gets corrupted. Since the following 100, after the first 100 are purely random creations. Since it would use the locked-wallet password as part of the generation, that maintains the random security. Because if they know your password, then you are screwed anyways.)

Having multiple wallets would be a nice touch too... (Selectable from within the client.)

Having a coin-specific wallet, would be even better... (Cap-wallet.dat, as opposed to all wallets just called wallet.dat, which makes it a pain to backup. Because you have to make each in a folder, or rename them all then rename them again to restore them.)

Even better if it did an auto-backup, to a different location, checking that the wallet was OK before doing a backup. (One bad section in a hard-drive, and your wallet is just gone. It never even knows it is corrupt until you try to reload it. Especially after a computer crash, which happens often when you leave your wallet open to mine all the time. Hard-drive caching is guilty of that corruption.)

Even if you restore an older wallet, if you had tx's with newer random addresses, those are just lost forever, because they didn't exist in the older wallet, and the chances of recreating that address again, randomly, are slim-to-none. (For those of us who use more receiving addresses than the wallets first 100, to identify sales. But again, all coins are like that, at the moment.)

The question remains: where is mullick?

Ah! The last block indeed matches, so I suppose it works as required. Thank you for the explanation Saves me a lot of time in constantly redownloading the entire blockchain.

Hi ScrappyD2o. Welcome to the forum and thanks for reporting the issue.

CAP has recently added a feature called advanced checkpointing. What BitCoin does is manually update the latest checkpoint in the client with each new client release. This checkpoint helps to secure the network. With BitCoin, sometimes a client update is not issued for months, so the checkpoint isn't updated either.

What advanced checkpointing adds is an external checkpoint server which the client checks after every block.  The regular checkpoint is still updated with each new client release, but security is enhanced further by verifying every block with the checkpoint server.

The message you are receiving pertains to this checkpointing.  Regular or advanced checkpointing are not required for the network to function properly and securely. They are an added security feature.  If your last synced block number in the client matches the one at http://bottlecaps.kicks-ass.net/block_crawler.php you have done everything right and can begin to use the client.

I'll contact Mullick, the main developer on the client to have him take a look at the checkpoint server. If you have any other questions, please don't hesitate to post.

This is normal, until he updates the checkpoint. There hasn't been any real issues with the chain, so a checkpoint wasn't actually required. (That is to ensure everyone is on the same chain. A default value from lite-coin, which few coins have "fixed" to compensate for the faster coins. Thus, it warns way to early than it should.)

You can ignore that warning. Though, they should all adjust it, and put auto-checkpoints.

To ensure you are on the right chain, if you have doubts, use cap-explorer.
http://bottlecaps.kicks-ass.net/block_crawler.php

I've redownloaded the BlockChain several times now, but I constantly get the message Checkpoint is too old.

BottleCaps v1.5.2.0-g32a928e-caps

tried:
Clean .conf file with only official nodes
No .conf and letting QT figure it out
Nodes list from one of the sites listed in the OP

Every single time: WARNING: Checkpoint is too old. Redownload Blockchain.

What can I do to fix this?

Also... More resources I am playing with...

(This is great for website payments, for those who have QR-Code scanner programs. Or for creating manual paper-wallets with the information from your wallet.)
PHP QR Code generator:
http://phpqrcode.sourceforge.net/

(Does not have CAP added to it. If you modify the other code, please modify this code too. Can be used for vanity-address generation.)
PHP Coin addresses generator:
GITHUB: https://github.com/zamgo/PHPCoinAddress

If someone wants to work on a paper-wallet, who knows what they are doing... Here is the link to BitCoins Javascript Paper-wallet, which was converted into a MinCoins Javascript Paper-wallet. (Warning, there is a lot of code to digest here. Also, it uses self-contained PNGs, as code. This allows it to run 100% as an html file on your desktop, without contacting the web for images or data. EG, you can run this offline.)

"Open Source JavaScript Client-Side MinCoin Wallet Generator"
GITHUB: https://github.com/stevenh512/minaddress.org
FILE:    bitaddress.org.html

DEMO: http://www.minaddress.org/

NOTES: This code can be easily modified to use with any HTML. I believe it simply needs the SEED changed and the VALID REGEX checking, along with the TEST ADDRESSES, to be used for CAP. (With the obvious textual changes, in the three languages, English, Spanish and French.)

If anyone does modify this, please throw it up as a branch to the original, or a branch to this one.

I answered my own question... There is no way to get account info without talking to a daemon.

I just have to get a fixed-IP for my other server, or use a DNS-updater. (For when it changes.)

Almost ready to add another service to CAPs. Just going to wait for the name issue to be resolved, before I continue.

Also, seems "Bottle" is more related to "Baby" than "Soda". Soda-caps and Beer-caps and Water-caps are not what is though-of when you say bottle-caps. That is another common thing I keep hearing when talking to random strangers about CAPs.

So, my final suggestion is now "CAPs", or "Digital-Caps", or "Cap-Coins", in that order of desire...

I threw-out "pop-caps" and "soda-caps", because that didn't help the image, when I suggested it to others in the public. I also got mixed responses from "Cappuccinos", as a currency name. Though, they all still liked the idea.

The biggest concern wasn't "Where do I cash them in", it was, "Where do I buy them". To this, I had no response to offer, due to the lengthy way to actually get them through shady, risky or complex methods. They didn't even ask how-much, just how...

Anyone sell bottlecaps for cash?

I don't think I saw anywhere to actually purchase bottlecaps. (Again, this leads back to the name issue, I imagine. Hard trying to convince someone that 1000 bottlecaps for $10.00 is not 1000 actual caps from bottles, for $10.00.)

I'll sell 1000 CAPs for $10.00 USD. No BTC exchange hassle. 2000 for $19.00.
Would be 900 and 1800 in a few weeks, for those same prices.

I think we should just call them "CAP". Thus, plural would be CAPs, and we still refer to them as cap-coins, which is sufficient, though stereotypical to being classic in name. (Digital-Caps, I suppose, would work too, as long as the bottle-cap branding was removed and replaced with something-else. With CAP being reference to "Limit", or "Apex", Digital-Limits, Digital-Apex... Upper bounds.)

In any event, before I go forward with this whole market, I need to know what we want for branding image, for marketing.

We need an official poll, with the ability to add suggestions. (Not a forum-poll.)

We still have a while longer, operating under the shadow of BTC's new-found price-hike fame.

How do we pay with CAP coins? There is no pay-selection, or link to the payment-processor...

Don't forget to add the link to the CoinPayments.net site... (As opposed to just saying in a graphic-image.)

"Alt coin payments accepted through CoinPayment.net" <--- at-least, as a searchable text link, or google has a hard time seeing your shop as valid for alt-coin payments. (That also improves search-rankings, since it is crypto-coin-relevant by back-links.)

Might also want to explain what the "C" thing is... I am not sure what currency that is, but CAP is mostly USD holders. Might want a USD option/price. If that is a foreign currency, those purchases might not be valid to USA holders, as things like x-box-live cards seem to be country-specific.

Also, explain what coins CoinPayments.net uses... Eg, CAP, BTC, LTC, FTC, PCX... (By the way, you know you can use your cryptsy account as a payment gateway to accept any coin, right... Using the API and your account information for the deposits.)