Silence is golden, but updates are better:  1.4 coming soon. |
|
|
|
|
Cryptsy has given the greenlight that their DBL client is updated and back online. Will be doing some tests with it tonight/tomorrow and if all goes well, on to the next step!
|
|
|
|
Its in main.cpp in most coins and looks something like this: static CBigNum bnProofOfWorkLimit(~uint256(0) >> 20); // starting difficulty is 1 / 2^12 |
|
|
|
What about exchange?
As per reply from "Mullick" at Cryptsy from yesterday, its actively being worked on and shouldn't be much longer until its back in business. If you want to see DBL on other exchanges, that's up to the community. |
|
|
|
So glad to see things turn around for Un! Feel free to use my Un or OFF addy in my signature to send me a few, they are the only coins worthy of signature status  |
|
|
|
|
How about some source code? Not everyone uses Windoze.
~edit major instamine going on, been live for less than 6 minutes and there's 600+ blocks already. Why no source? Premine?
|
|
|
|
|
WTS: 250K ChC PM for offers...
|
|
|
|
|
Nice mix of algorithms here! Hope to see this one take off, the wallet customizations are quite visually exciting too.
|
|
|
|
If i have 100 uno in my wallet, but the chain says i have 75 for the one address, is that because i sent uno to my wallet using two addresses? The chain only accounts 75 of that 100 uno for that one address?
Yes, each wallet.dat can hold multiple addresses--the GUI wallet or daemon will combine those balances, but the blockchain explorer won't. Coincontrol will be included in a future build which will allow you to see the individual balances by address per wallet.dat. |
|
|
|
Those tiny micro sell orders on Cryptsy just piss me off. Such clutter, and it obscures the order book.
At this moment on Cryptsy, I can only see the sell book from 0.00312778 to 0.00349278. It's all clogged up with junk orders 1 satoshi apart. Its hard to trade that mess, you can't see what's ahead.
I have a dream that some day we the UNO community will have our own just UNO market. [also because in the future setting up an exchange will be open source copy-pasta easy]
[and we all be uno bizillionaries by then so can kickstart it No Problem]  Then we can have these markets: 1 satoshi / uno
1 kilogram uno/btcuno/drk uno/naut uno/veri,bc,doge etc uno/$ Excellent we're keeping the scientific notification, we must not deviate. By the way, just pushed a nice big update for you on Github, including alertkeys, makekeypair, working test and regresssion settings and some general housekeeping. https://github.com/unobtanium-official/Unobtanium/pull/6Working on something a bit more fancy for the wallet in the way of graphical utilites now, but will need a couple days to get it running smoothly, I'm not a Qt master quite yet |
|
|
|
|
Checking in! This is my first PoS stake like this, very excited.
|
|
|
|
Ah, so only checkpoints... I was thinking about new code base...  Yes, it will happen but baby steps |
|
|
|
Here we have Doubloons v11 (Queen Anne's Revenge):  https://www.dropbox.com/s/s774sa1se9bzgiv/Doubloons-Qt-v11.rarTo ensure you're on the right chain, check with http://explorer.doubloons.net and verify block height once your client finishes synching. You may experience slow synching as there are a lot of blocks orphaned around 267200, if needs be, you can clear your %appdata%\Doubloons folder (but not your wallet.dat!) and resynch. Adding this to your .conf may help as well: banscore=1
addnode=explorer.doubloons.net
addnode=seed1.coinlab.info
addnode=seed2.coinlab.info
addnode=seed3.coinlab.info
addnode=seed4.coinlab.info This can help synch the correct blocks and mirrors the seednodes internal to this new v11 client. Since shakezula's gone on to deeper waters, we have no way to update the main post, so pass this info around to your DBL compadres! Cryptsy has been notified to upgrade and we anticipate they should be back on the correct chain in a few days time. Once transactions are flowing and blocks are happy again, we'll proceed to the next step of bringing the code up to more recent levels and possibly hard-forking for diff or coin-swapping to a new algo, but again, this a step in the right direction. We'll get DBL riding the high seas again! |
|
|
|
Is it not easier just put DBL patches into 0.9 LTC client?
That's what we'd like to do but we want to rectify the forking first. From some extensive fiddling with this last night here's where we stand: The_Catman's client doesn't reliably want to synch past block 267269 on some machines. We think this is where the first fork started. Explorer.doubloons.net is the authoritative chain at this point with 324072 (and climbing) blocks. This is the longer chain and should win-out. Cryptsy hasn't responded to us about which block height they are at--but as mentioned we've already begun discussions with them about getting DBL fixed and they are receptive. Here's what we're looking at doing: The explorer's chain will be considered authoritative. An updated DBL client which has correct checkpoints and additional seednodes will be released in the next day or two. This client will not be a hard fork (yet) and will be geared at getting everyone back in-synch with the new seednodes and explorer. Once Cryptsy is updated to the newest code and back in-synch, we'll push out an updated-updated version of the client which will shut off the old nodes from connecting AND bring the code-base up to more recent standards. Watch for the new client to be here in the next day or two! |
|
|
|
|
Ok, so long time no fixes for this client. After a botched diff adjustment by The_Catman and subsequent slacking of any further deveopment and current forking, we think its time we cut our losses and do a complete overhaul of this chain.
We have contacted Cryptsy about the following plan and have received tentative buy-in from them:
Create a new Doubloons Client, forking to something new, X11 or X8 are both attractive options.
Client will have tx messaging in the system and use the same public key addressing as the old blockchain.
We'll manage a swap out 1:1 of the coins, making it as easy as possible, send in your old coin, get new coin back at same address (or new) and import your privkeys keeping your existing DBL addresses intact. Swap out will be managed and verifiable via block chain and transactions and we won't be changing the existing total of coins.
So here's notice that is our plan and we're putting in to motion over the next week or two. A new client and thread will be created and you'll all get the giggles being able to mine and trade DBL's again!
|
|
|
|
|
Sure, 30K of DOGE is good:
D9i7U4za6FpzmScY2XyBLt6aFoQA62oLRr
Got TV? PM me your access code.
|
|
|
|
I was able to compile your coin using the old Shakezula deps:  It appears your -qt.pro doesn't have the right lines or something to that effect, because I plugged them in directly out of the foocoin (what you're creating here) and voila, it worked! Here's the Qt: https://www.dropbox.com/s/5itl13zuy70v4au/Flightcoin-Qt.rarWould be willing to TeamViewer with you and show you how I got it working for a bit of BTC.... |
|
|
|
|
Show Posts
