Known Issues on Yumekawa Wallet

draft Slow download at first startup there are a few node at this moment. automatic download is slow but much safer. if you need fastest download spee...

cryptozeny · 2019-09-22T07:50:36+00:00

draft Slow download at first startup there are a few node at this moment. automatic download is slow but much safer. if you need fastest download spee...

Known Issues on Yumekawa Wallet

cryptozeny

draft

Slow download at first startup
- there are a few node at this moment.
- automatic download is slow but much safer.
- if you need fastest download speed, you can add following nodes:
```
    1node.sugarchain.org
    1explorer.sugarchain.org
    1seed.sugarchain.info
    2seed.sugarchain.info
```
Transaction too large
https://github.com/sugarchain-project/sugarchain/issues/28
- If you encounter this issue, you can simply fix it with recreate wallet.dat. Its UTXO part of the BTC. Do not worry about this.
- This issue will be fixed in next Schnorr Signature update.
- It's already known issue: https://github.com/bitcoin/bitcoin/issues/6522
- You should back up your wallet.dat periodically.
Aborted (core dumped) for safety
- if you got Aborted (core dumped), sugarchaind will be shutdown. but its normal behavier, do not worry and just restart daemon. I will fix this issue better. Alexander did with exit() and i think its better. in next update it will be fixed.
- code
```
    // yespower
uint256 CBlockHeader::GetPoWHash() const
{
    uint256 thash;
    CDataStream ss(SER_NETWORK, PROTOCOL_VERSION);
    ss << *this;
    yespower_params_t yespower_1_0_sugarchain = {
        .version = YESPOWER_1_0,
        .N = 2048,
        .r = 32,
        .pers = (const uint8_t *)"Satoshi Nakamoto 31/Oct/2008 Proof-of-work is essentially one-CPU-one-vote",
        .perslen = 74
    };
    if (yespower_tls( (unsigned char *)&ss[0], ss.size(), &yespower_1_0_sugarchain, (yespower_binary_t *)&thash) ) {
        abort();
    }
    return thash;
}
```
- This Aborted (core dumped) means you got wrong hash, and daemon refused this hash. Its necessary for security. This protect us from hash attacking.
- in other words, if your pool attacked by wrong (faked) hash attacking, your pool will be shut down, and its normal intended behavier. suggested by original yespower author.

Slow update balance: update total balance every 1 minute interval

description (sorry but in korean)

Sugarchain: GUI: reduce lock call: pollBalanceChanged

fix: QT Wallet Freeze resolved.

Do update Balances in QT GUI every 60 sec. Instead of every blocks.

Description in Korean:
TX 이력이 많은 Large wallet 예를들면 마이닝풀, 에서QT지갑의 잔액 상황을 보여줄때 딜레이가 발생하고 이것은 5초 마다 발생하는데 이 딜레이 셧다운이 3초이상으로 길어지면 거의 계속 멈춘상태로 QT지갑을 사용하기 어려워진다.

그래서 업데이트 간격을 every block 에서 12 blocks (약 60초) 간격으로 늘린다.

대신 잔액 업데이트가 1분간격으로 이루어지며 딜레이로 인한 랙장애는 없다. 참고로 비트코인은 10분에 1회 이루어 진다.

이 해결책은 원본 비트코인지갑의 known issue에 대한 해결책이며 workaround에 속한다. 비트코인 개발자들의 지속적인 업데이트를 주시한다.

증상:
QT지갑의 잦은 랙으로 인한 사용불가 현상 (경미)
마이닝풀에서 해시가 늘어나지 않는 현상 (심각)

해결된것:
QT지갑의 지연이 60초 간격으로 lockMain 주기를 완화시킴으로 해결.

Ref:
Bitcoin-ABC/bitcoin-abc#49
bitcoin/bitcoin#10504
bitcoin/bitcoin#15148
bitcoin/bitcoin#10349
bitcoin/bitcoin#5851
bitcoin/bitcoin#13612

code

// FIXME.SUGAR // SURE?
void WalletModel::pollBalanceChanged()
{
    // Get required locks upfront. This avoids the GUI from getting stuck on
    // periodical polls if the core is holding the locks for a longer time -
    // for example, during a wallet rescan.
    TRY_LOCK(cs_main, lockMain);
    if(!lockMain)
        return;
    TRY_LOCK(wallet->cs_wallet, lockWallet);
    if(!lockWallet)
        return;

    if(fForceCheckBalanceChanged || chainActive.Height() != cachedNumBlocks)
    {
        fForceCheckBalanceChanged = false;

        // BEGIN - DEBUG for checking height?
        printf("  %d = height \n", chainActive.Height());
        printf("  %d = cached \n", cachedNumBlocks);
        printf("height - cached = %d \n", (int)(chainActive.Height() - cachedNumBlocks));
        // END - DEBUG for checking height?

        // FIXME.SUGAR // SURE?
        // update every blocks >> 12 blocks // 5*12 = 60s
        if(chainActive.Height() - cachedNumBlocks >= 12)
        {
            // BEGIN - DEBUG for checking polled?
            printf("\033[0;31m  pollBalanceChanged:  \033[0m \n"); // red
            printf("height - cached = %d \n", (int)(chainActive.Height() - cachedNumBlocks));
            // END - DEBUG for checking polled?

        // Balance and number of transactions might have changed
        cachedNumBlocks = chainActive.Height();

        checkBalanceChanged();
        if(transactionTableModel)
            transactionTableModel->updateConfirmations();
        }
    }
}

cryptozeny

Someone claimed about our slow download speed. we should make it faster. @volbil is also claimed. its the high priority job for now.

todo:
[x] make download speed faster
[x] resolving dropout when searching nodes

Current known issue on Yumekawa is 1) Slow download on startup. It will fix in next update. Thanks to report. @everyone

Slow download at first startup
- there are a few node at this moment.
- automatic download is slow but much safer.
- if you need fastest download speed, you can add following nodes:
```
    1node.sugarchain.org
    1explorer.sugarchain.org
    1seed.sugarchain.info
    2seed.sugarchain.info
```

https://forum.sugarchain.org/d/26-known-issues-on-yumekawa-wallet

cryptozeny

Known Issues:

Transaction too large: This is a part of BTC and will be fixed in next Schnorr Signature update.
Slow update balance on wallet: Update total balance every 1 minute (12 blocks) interval. This slow is a part of BTC and this fix is a (nice) workaround for now.
Poor performance on ARM CPUs (32/64-Bit): ARM optimization for Yespower disabled for now. TODO
Poor performance on 32-Bit OS: SSE2 for Yespower disabled for now. Please use 64-bit for best performance.

patipravat

how to restore wallet?

cryptozeny

patipravat stop yumekawa, just put your wallet.dat back. and restart yumekawa.

iosgithub555

cryptozeny
wallet.dat In which path?

Lexsinn

Hello i do not get how to ad node becaus e sync takes a long time how can i speed it up?

cryptozeny

Lexsinn how can i speed it up?

we are working on this speed up. i expect 2x faster than before in near future.

akaolly

any help to resore my wallet from the wallet.dat i have saved its a fresh wallet i have downloaded but want to enter the dat to restore but dont know where i have to do this any help appreciated

yeruisheng

Hello friends, when my latest wallet synchronizes the block, I have been unable to connect to the node to synchronize. The latest block time is still about eight or nine days ago, and then it will not be updated for a few days. Eight days ago, 16.3.36 was released. Version of the wallet, I think it’s because of this problem that my wallet can’t be synced. Before, I used the 16.3.34 version of the wallet. What should I do? Thank you. In addition, I’m using the osx version of the wallet.