Topic: [ANN] [USDe] Unitary Status Dollar eCoin $$ IMPROVED Halving | KGW Fix Update!!! - page 94. (Read 578463 times)

what about other exchanges? which ones are on the right chain?

USDe Community,

After careful consideration, strategic review and many long drawn out discussions, the board members of the USDe Coin have decided to intentionally fork the block chain.  This fork will be done for several reasons:

• To protect the value and integrity of USDe.  USDe was created with the consumer in mind, i.e., to be accessible to all, easy to use, with fast transactions and accepted by numerous retailers. USDe was not fashioned so that miners can attempt to guess or manipulate blocks.
• USDe was also created with the intention of not only retaining its value, but with the ideal of gaining greater value over time. The goal of USDe is to succeed by becoming the standard currency for online transactions and eventually, shopping at your neighborhood grocery store.

Approximately 8 days from today, the USDe block chain will fork at exactly block # 107,500. The goal of the fork is to cease the paying out of bonus / superblocks in the amounts of 5,000, 10,000, 20,000, 50,000 and 100,000 USDe. These superblocks will be removed permanently. Henceforth, after this fork, all blocks will payout 4,000 coins each until the scheduled block reward halving.

Upon the block chain reaching approximately 1/3 of all coins mined, the block chain will again halve the value to 2,000 coins. When in the future the block chain reaches 2/3 of all coins mined, the block will again split to a payout of 1,000 coins until all remaining coins have been mined.

We will be in touch with every USDe pool, service provider, store and exchange to make sure that this update goes smoothly. If there is a store, exchange or USDe-related service provider that is not listed here or may be obscure, please let us know who they are, so that we can make sure they are on board with the update.

Thank you for your continued support!
The USDe Coin Board

P.S. Our official source code and all updates can be found here:
https://github.com/usde-project/usde

The Windows Wallet links have been updated on this thread and the http://usd-e.com Web Site.

Go USDe!

Update on Poloniex-------

1.  The exchange has been contacted about potentially (they are) being on the wrong side of the recent fork at 91K.
2.  They are escalating this to Tristian the lead owner/developer for the Exchange to fix; however, it may take a bit.  They of course are dealing with their recent BTC theft of 12.3% of all BTC that was on their exchange also right now.

As far as I understand, you can deposit not their (at the risk of the BTC theft adjustment that may occur) and continue to trade USDe; however, you should wait to withdrawal any USDe until they get on the proper side of the fork.

I know our dev team is doing what is best for the coin, the KGW, and future changes so hang in there.  These improvements along with our addition to other exchanges going forward will only help USDe grow stronger.

-T

EDIT:  They just responded again with so hopefully fixed soon:

"
Hi Travis ####,

Okay, just this second I made him aware of it; and I await his response.  Thank you very much Travis for being so helpful!  I really appreciate it!  Angela
"

I must admit, for me it is also confusing.
Glad we could figure it out.
I should start asking a fee for this @ DEV team .
Time to go to bed.

I'm not sure already, what happened. But I don't update my pool client (don't sure now in this, may be I have update it and forget... ).
When one client write me, what transactions don't show at Poloniex. I have found, what developers created new GitHUB and noticed, what I can't find transactions on main block explorer. When I rebuild client from new GitHUB, delete block chain, started it and stay in same chain as before.

So, may be, I have updated USDe wallet before and forget about it (updated about 3-4 wallets last days).

But any way. P2Pools, explorer and poloniex (not sure, but payments not funded) on wrong chain.

Team-

1.  Please keep voting at Mintpal to add USDe, we will be one of the next couple coins there.
Mintpal is getting good reviews and has less "crap coins" on it to dilute training.

2.  We will be added to Cryptsy vote page soon.  We have some catching up to do there.
https://www.cryptsy.com/coinvotes

http://cryptexplorer.com/chain/USDe
http://altexplorer.net/chain/USDECoin
https://www.poloniex.com/exchange (probably)
http://solidpool.org/#usde

So in your debug log does it say:


Latest client version is: v1.0.1.0-g3aaa7ba-beta

Time for my 2 cents.
It was biggest mistake to change github. WHY?

Most service with many daemons monitor file version.h and clientversion.h for changes in github to check latest version.
Service with 100 daemons don't checks forum every day.

PS: I check my debug log. And most clients connecting with Wallet version 60002.

OK, lets try this one then:

getblockhash 92000
e28ed3dcc0c247382804306dcabd3510fb058c3368f4d04c5492d2af2d32160d

I am currently solo mining with this client > it is running KWG (difficulty changes every block, now @ 3)

how do you find what 7690ee490b68485355d8046c47eabe16a8c2063798f54ef57c1157ac934d1264  has KGW ?
Block 7690ee490b68485355d8046c47eabe16a8c2063798f54ef57c1157ac934d1264 was find in my pool with old client (my fault).


https://altexplorer.net/block/f8c0a5e10b9fd1a9b338c1e1f6573c7b557ac2d445581f7d7113146ccf9bde28

Again, 7690ee490b68485355d8046c47eabe16a8c2063798f54ef57c1157ac934d1264 is the right chain.
It has the KGW in it!

Let me try to summarize what you are saying:

- New client accept block with KWG fix  > correct because the new client was build with KWG from block 91000 onwards
- Because blocks from old clients have higher minimum difficulty > do not really understand, but current blocks from old client have a lower difficulty because not many people are mining them anymore (OLD Client)
- when need..... longer now > not sure what you mean here
- Client version check and devs > agree

Corrected, sorry for my English

Ok, you have noticed it finally now, I can go sleep.
You can check you chain in debug window or RPC.

getblockhash 91001

if you get f8c0a5e10b9fd1a9b338c1e1f6573c7b557ac2d445581f7d7113146ccf9bde28 - your client on right chain
if you get 7690ee490b68485355d8046c47eabe16a8c2063798f54ef57c1157ac934d1264 - you on wrong chain.

But I don't know now switch to new chain. Most nodes on wrong chain, so if you delete files and download it again in most cases you'll stay here.
Wallet with checkpoints need to be recompiled to accept only needed chain

I really do not understand your first sentence, please try to be more clear.

New client with KWG fix accept old blocks  because blocks from old clients have higher minimum difficulty, than KWG  need and this chain is longer now.
As usual last days, developers not added minimum client version check for new clients, so where is a problem now...

At block 91000 KGW was added > therefore a new wallet was required from this point onwards.

Coinium also on wrong chain

http://usde.coinium.org/index.php?page=statistics&action=pool

Next Network Block    92961    (Current: 92960)

Poloniex and blockexplorer and P2Pools have maxblocks 92,768 now.
https://altexplorer.net/chain/USDECoin
http://solidpool.org:9448/static/

All mpos pools mine another chain with max height 92957.
This chain started from block 91001.
http://usde.poolerino.com/index.php?page=statistics&action=pool
http://usde.blockchasers.com/index.php?page=statistics&action=pool
and so on

Look again at my post above and tell me which one is with KGW and which one is still on the old wallet/chain......

THe chain with KGW is the right chain!

I think the DEV team should contact all to make sure everyone is on the right chain!!!!! HURRY!