Maybe it's because of using too much swap?
Generally, the memory of arm device is not higher than 2G, but you need 3G
Large amount of disk IO will consume large amount of CPU
This may not be obvious on the PC, but the CPU performance of arm is too low, so the speed will be significantly reduced
If sdcard is used as swap, it is even more inconceivable
@crypt?zeny What is your arm test environment like?

test required

/2 is not meaningful i guess

its 17% faster IBD sync. but less safer than before.

https://github.com/sugarchain-project/sugarchain/pull/80/files

Segmentation fault      (core dumped)
Makefile:3757: recipe for target 'qt/test/test_bitcoin-qt' failed

AR qt/libbitcoinqt.a
OBJCXXLD qt/bitcoin-qt
CXXLD qt/test/test_bitcoin-qt
/bin/bash: line 1: 12065 Segmentation fault (core dumped) /bin/bash ../libtool --silent --tag=CXX --mode=link g++ -std=c++11 -Wstack-protector -fstack-protector-all -fPIC -g -O2 -Wall -Wextra -Wformat -Wvla -Wformat-security -Wno-unused-parameter -pthread -Wl,-z,relro -Wl,-z,now -pie -o qt/test/test_bitcoin-qt qt/test/qt_test_test_bitcoin_qt-compattests.o qt/test/qt_test_test_bitcoin_qt-rpcnestedtests.o qt/test/qt_test_test_bitcoin_qt-test_main.o qt/test/qt_test_test_bitcoin_qt-uritests.o test/qt_test_test_bitcoin_qt-test_bitcoin.o qt/test/qt_test_test_bitcoin_qt-paymentservertests.o qt/test/qt_test_test_bitcoin_qt-wallettests.o wallet/test/qt_test_test_bitcoin_qt-wallet_test_fixture.o qt/test/qt_test_test_bitcoin_qt-moc_compattests.o qt/test/qt_test_test_bitcoin_qt-moc_rpcnestedtests.o qt/test/qt_test_test_bitcoin_qt-moc_uritests.o qt/test/qt_test_test_bitcoin_qt-moc_paymentservertests.o qt/test/qt_test_test_bitcoin_qt-moc_wallettests.o qt/libbitcoinqt.a libbitcoin_server.a libbitcoin_wallet.a libbitcoin_zmq.a -lzmq libbitcoin_cli.a libbitcoin_common.a libbitcoin_util.a libbitcoin_consensus.a crypto/libbitcoin_crypto.a univalue/libunivalue.la leveldb/libleveldb.a leveldb/libleveldb_sse42.a leveldb/libmemenv.a -L/usr/lib/x86_64-linux-gnu -lboost_system -lboost_filesystem -lboost_program_options -lboost_thread -lboost_chrono -lQt5DBus -lQt5Core -lQt5Test -lQt5Core -lQt5Network -lQt5Widgets -lQt5Gui -lQt5Core -lqrencode -lprotobuf -pthread -lpthread -ldb_cxx-4.8 -lssl -lcrypto -lminiupnpc secp256k1/libsecp256k1.la -levent_pthreads -levent -levent
Makefile:3757: recipe for target 'qt/test/test_bitcoin-qt' failed
make[2]: *** [qt/test/test_bitcoin-qt] Error 139
make[2]: *** Waiting for unfinished jobs....

ResistancePlatform/resistance-core@64ee78a

my question:

solardiz suggested this abort() last year, but it seemed something is changed.

ResistancePlatform/resistance-core@48e6c14
ResistancePlatform/resistance-core@6732897
ResistancePlatform/resistance-core@2166402
ResistancePlatform/resistance-core@75a437e

we do not use this sigs yet.

this should be 100000*120

dgenr8/chain2@50efdf5

https://miningpoolstats.stream/chain2

Bitcoin XT

uint256 CBlockHeader::GetPoWHash() const
{
    static const yespower_params_t params = {
        .version = YESPOWER_1_0,
        .N = 4096,
        .r = 32,
        .pers = NULL,
        .perslen = 0
    };
    uint256 hash;
    CDataStream ss(SER_NETWORK, PROTOCOL_VERSION);
    ss << *this;
    if (yespower_tls((const uint8_t *)&ss[0], ss.size(), &params, (yespower_binary_t *)&hash)) {
        fprintf(stderr, "Error: CBlockHeader: failed to compute PoW hash (out of memory?)\n");
        exit(1);
    }
    return hash;
}

ResistancePlatform/resistance-core@64ee78a

  CXX      crypto/libbitcoinconsensus_la-sha512.lo
  CC       crypto/yespower-1.0.1/libbitcoinconsensus_la-sha256.lo
  CC       crypto/yespower-1.0.1/libbitcoinconsensus_la-yespower-opt.lo
crypto/yespower-1.0.1/yespower-opt.c:59:2: warning: #warning "SSE2 not enabled.  Expect poor performance." [-Wcpp]
 #warning "SSE2 not enabled.  Expect poor performance."
  ^
  CXX      crypto/libbitcoinconsensus_la-sha256_sse4.lo

add -msse2 to GITIAN builds

https://github.com/google/boringssl/blob/master/util/32-bit-toolchain.cmake
-m32 -msse2

Alexander said it's not an actual problem, however it's an issue anyway :)

[TRAVIS] warning: -fPIC ignored for target (all code is position independent) [enabled by default]

• 1

CC src/libsecp256k1_la-secp256k1.lo
src/secp256k1.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/**********************************************************************
^

• 2/3

CC crypto/yespower-1.0.0/crypto_libbitcoin_crypto_a-sha256.o
crypto/yespower-1.0.0/sha256.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/-
^
CC crypto/yespower-1.0.0/crypto_libbitcoin_crypto_a-yespower-opt.o
crypto/yespower-1.0.0/yespower-opt.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/-
^

• 4/5

CC crypto/yespower-1.0.0/libbitcoinconsensus_la-yespower-opt.lo
crypto/yespower-1.0.0/sha256.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/-
^
CXX crypto/libbitcoinconsensus_la-sha256_sse4.lo
crypto/yespower-1.0.0/yespower-opt.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/-
^

• 6/7

CC src/exhaustive_tests-tests_exhaustive.o
src/tests.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/**********************************************************************
^
src/tests_exhaustive.c:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
/***********************************************************************
^

cryptozeny/sugarchain-v0.16.3#65

2020-01-29 09:58:31 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 578e8bf7623c13dd7f64054a1a22b71d1248b51547d027c33d673f8241e46f75, time-too-new, block timestamp too far in the future (code 16)
2020-01-29 09:58:31 ERROR: invalid header received

all peers banned

what do you think?

Reward for Yumekawa Beta Testers

i hope this 29rc5 will be the final beta. pls test this version before public🔥 we can reward and can be multiple rewarded.

Conditions:

• 1. Fresh new install Yumekawa 29rc5 on new machine, or reinstall whole thing.
• 2. Win 32 or 64-bit 3k
• 3. Linux 32 or 64-bit 5k
• 4. OSX 7k
• 5. Testers only Sugar Team
• 6. Should Sync done, and attach some screenshots
• 7. If you found an ISSUE or PROBLEM, additional reward at least 10k++ each

Testing Fields:

• OS (Win64, Linux64, OSX)
• Version
• Traffic
• Peers
• Synctime (optional)
• Transaction Test (optional)
• Reward Address (your sugar address)

Warning:

When you reinstalling, backup your wallet.dat on following folder.

Windows: C:\Users\YourUserName\Appdata\Roaming\Sugarchain\
Linux: ~/.sugarchain/
OSX: ~/Library/Application Support/Sugarchain/

https://github.com/sugarchain-project/sugarchain/releases/tag/v0.16.3.29rc5-071adf9

addressindex is originally suggested by
https://github.com/bitpay/insight

BTC declined merge into master, but they want to keep another repo.
bitcoin/bitcoin#10370

but its enabled only with -addressindex like txindex=1 and its bool so RAM usage is not affected
https://github.com/sugarchain-project/sugarchain/blob/API-addressindex/src/validation.cpp#L218

ZEC and RES have also addressindex
https://github.com/ResistancePlatform/resistance-core/blob/master/src/addressindex.h

if we merge this AddressIndex into master, i wanna do after Yespower PoW cache is finished. this is safer IMO.
@volbil

@rplant8

1st daemon (default -datadir location)

./src/qt/sugarchain-qt -rpcuser=rpcuser -rpcpassword=rpcpassword -server=1

2nd daemon

./src/qt/sugarchain-qt -rpcuser=rpcuser -rpcpassword=rpcpassword -server=1 -resetguisettings -datadir="/home/ak/.sugarchain2-test/" -port=54230 -rpcport=54229

CMD

./src/sugarchain-cli -rpcuser=rpcuser -rpcpassword=rpcpassword -datadir="/home/ak/.sugarchain2-test/" getblockcount
1506409

OSX traffic is 80% more than WIN. what causes this traffic increasement on only OSX?

LINUX: 4 GB
WIN: 6 GB
OSX: 10 GB

• OSX
  
  

• WIN64
  
  

https://1explorer.sugarchain.org/tx/%s

actual blockchainsize is 1.4 GB, but during IBD it uses too much traffic (around 40 GB). so mobile users data limit ran out too fast.

Fais Sheikh, [09.01.20 12:48]
How big sugar wallet size ?

Fais Sheikh, [09.01.20 12:48]
100 gb?

Fais Sheikh, [09.01.20 12:49]
I kept it last night to sync only 33%

Fais Sheikh, [09.01.20 12:49]
It’s 38 gb was download

Volbil, [09.01.20 12:50]
[In reply to Fais Sheikh]
0_o

Volbil, [09.01.20 12:50]
Are you sure about 38 gb?

Volbil, [09.01.20 12:50]
Not mb?

Volbil, [09.01.20 12:51]
[ Photo ]

Fais Sheikh, [09.01.20 13:06]
I kept for sync idk what went wrong

Fais Sheikh, [09.01.20 13:07]
[ Photo ]

Fais Sheikh, [09.01.20 13:07]
33% only

Fais Sheikh, [09.01.20 13:07]
I closed it cuz I had only 44gb data left lool

Fais Sheikh, [09.01.20 13:07]
Fkup

Fais Sheikh, [09.01.20 13:09]
Idk how this happened damn

Fais Sheikh, [09.01.20 13:09]
I had nothing else to sync or download

Fais Sheikh, [09.01.20 13:09]
All data eaten

Volbil, [09.01.20 13:13]
@cryptozeny we should investigate it

Volbil, [09.01.20 13:13]
@fireboy299 can you check what is inside your .sugarchain folder?

Fais Sheikh, [09.01.20 13:14]
at my wallet its only 1.6gb

Fais Sheikh, [09.01.20 13:14]
but my hdd says space went down

Fais Sheikh, [09.01.20 13:14]
not sure what file was getting donwloaded

Fais Sheikh, [09.01.20 13:15]
[ Photo ]

Volbil, [09.01.20 13:15]
[In reply to Fais Sheikh]
I think this is your network traffic

Fais Sheikh, [09.01.20 13:16]
back to 1.2?

Volbil, [09.01.20 13:16]
Not actual disk space

Fais Sheikh, [09.01.20 13:16]
NOPE

Fais Sheikh, [09.01.20 13:16]
i kept nothing else to sync

Fais Sheikh, [09.01.20 13:16]
single lap

Fais Sheikh, [09.01.20 13:16]
singlr user

Fais Sheikh, [09.01.20 13:17]
its my protable net

Fais Sheikh, [09.01.20 13:17]
so i use for lap only

Fais Sheikh, [09.01.20 13:17]
limited gb

cryptozeny, [09.01.20 13:18]
[In reply to Fais Sheikh]
@Volbil yeah i noticed duplicated download. it download multiple times.

Fais Sheikh, [09.01.20 13:19]
where is this file

Fais Sheikh, [09.01.20 13:19]
i need to remove

cryptozeny, [09.01.20 13:20]
[In reply to Fais Sheikh]
total blockchain size is currently around 1.5 gb. another is not stored

cryptozeny, [09.01.20 13:20]
[In reply to Fais Sheikh]
you downloaded, but its just check block verifying

cryptozeny, [09.01.20 13:21]
not stored in your disk

Fais Sheikh, [09.01.20 13:21]
ok

Fais Sheikh, [09.01.20 13:21]
what to do

Fais Sheikh, [09.01.20 13:21]
i dont need other stuff

cryptozeny, [09.01.20 13:22]
actually Yumekawa 4x times verifying all blocks since genesis.

Fais Sheikh, [09.01.20 13:22]
i just want to sync

Fais Sheikh, [09.01.20 13:22]
i will see where is this file at pc

cryptozeny, [09.01.20 13:22]
[In reply to Fais Sheikh]
if you have limited data transfer, just copy from already synced.

Fais Sheikh, [09.01.20 13:23]
where can i get it

cryptozeny, [09.01.20 13:24]
[In reply to Fais Sheikh]
Windows: C:\Users\YourUserName\Appdata\Roaming\Sugarchain\ Linux: ~/.sugarchain/ OSX: ~/Library/Application Support/Sugarchain/

cryptozeny, [09.01.20 13:24]
blocks and chainstate folder stotes all blockchain data

cryptozeny, [09.01.20 13:25]
but do noy delete wallet.dat its your actuall wallet

cryptozeny, [09.01.20 13:26]
you found an over traffic than current blockchain size. this will fixed in next release.

cryptozeny, [09.01.20 13:27]
[In reply to Volbil]
right. its network traffic

cryptozeny, [09.01.20 13:30]
[In reply to Fais Sheikh]
actually 1.4 gb for now. otherwise its jusy network traffic.
https://twitter.com/sugarchain_dev/status/1212483415410274307?s=19

cryptozeny, [09.01.20 13:31]
your traffic will be bigger than this to verify many times.

Fais Sheikh, [09.01.20 14:13]
Ok noted

Fais Sheikh, [09.01.20 14:13]
Sync where to download

barrystyle/dogecoin@d5c6e1d

by @barrystyle . thanks!

its too low

[Forwarded from Raku Ten]
I suggest when running wallet to add parameters to keep the debug.log, a lot of people don't need it

[Forwarded from Volbil]
I guess we can set it to False

[Forwarded from Volbil]
And add flag which will enable it

util.cpp

following options

• reduce size significantly
  • mostly UpdateTip: new best=
• disable debug.log by default
  • make an option for devs to debug
• -shrinkdebugfile as default

Assertion failed: (vch.size() == sizeof(data)), function base_blob, file uint256.cpp, line 16.

on OSX

@volbil

wallet.dat cannot recognize on PoW cache version
https://github.com/sugarchain-project/sugarchain/tree/v0.16.3.25rc1-6048eba

this issue occured only on Win64, but Linux64 is fine. i will investigate on this issue soon. not tested on OSX yet.

Win64: crashed
Linux64: fine
OSX: not tested

@volbil

less than linux64

ResistancePlatform/resistance-core@f84f9d6

libbitcoin_common_a_CFLAGS = $(AM_CFLAGS) $(PIE_FLAGS) -O2

try 120x

i need some tutorial @volbil

SUGAR (6 + 5)

// yespower
crypto/yespower-1.0.1/yespower-opt.c:57:2: warning:
crypto/yespower-1.0.1/yespower-opt.c:530:2: warning:
crypto/yespower-1.0.1/yespower-opt.c:57:2: warning: (duplicated)
crypto/yespower-1.0.1/yespower-opt.c:530:2: warning: (duplicated)
pow.cpp:66:14: warning:
pow.cpp:64:33: warning:
// btc
key.cpp:51:23: warning:
key.cpp:57:23: warning:
key.cpp:71:37: warning:
leveldb/util/logging.cc:58:40: warning:
leveldb/port/port_posix.cc:60:15: warning:

BTC (5)

key.cpp:51:23: warning:
key.cpp:57:23: warning:
key.cpp:71:37: warning:
leveldb/util/logging.cc:58:40: warning:
leveldb/port/port_posix.cc:60:15: warning:

SUGAR FULL LOG

$ make -j8 | grep "warning:"
crypto/yespower-1.0.1/yespower-opt.c:57:2: warning: #warning "Note: AVX and XOP are not enabled.  That's OK." [-Wcpp]
 #warning "Note: AVX and XOP are not enabled.  That's OK."
  ^
crypto/yespower-1.0.1/yespower-opt.c:530:2: warning: #warning "Note: using x86-64 inline assembly for pwxform.  That's great." [-Wcpp]
 #warning "Note: using x86-64 inline assembly for pwxform.  That's great."
  ^
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')
pow.cpp:66:14: warning: #warning "Note: 'pindexLast->nHeight >= params.nPowAllowMinDifficultyBlocksAfterHeight.get()'  That's OK."; [-Wcpp]
             #warning "Note: 'pindexLast->nHeight >= params.nPowAllowMinDifficultyBlocksAfterHeight.get()'  That's OK.";
              ^
pow.cpp: In function ‘unsigned int GetNextWorkRequired(const CBlockIndex*, const CBlockHeader*, const Consensus::Params&)’:
pow.cpp:64:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
             pindexLast->nHeight >= params.nPowAllowMinDifficultyBlocksAfterHeight.get()) // FIXME.SUGAR
                                 ^
key.cpp: In function ‘int ec_privkey_import_der(const secp256k1_context*, unsigned char*, const unsigned char*, size_t)’:
key.cpp:51:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (end - privkey < lenb) { // FIXME.SUGAR // BTC issue
                       ^
key.cpp:57:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (end - privkey < len) { // FIXME.SUGAR // BTC issue
                       ^
key.cpp:71:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (oslen > 32 || end - privkey < oslen) { // FIXME.SUGAR // BTC issue
                                     ^
ar: `u' modifier ignored since `D' is the default (see `U')
crypto/yespower-1.0.1/yespower-opt.c:57:2: warning: #warning "Note: AVX and XOP are not enabled.  That's OK." [-Wcpp]
 #warning "Note: AVX and XOP are not enabled.  That's OK."
  ^
crypto/yespower-1.0.1/yespower-opt.c:530:2: warning: #warning "Note: using x86-64 inline assembly for pwxform.  That's great." [-Wcpp]
 #warning "Note: using x86-64 inline assembly for pwxform.  That's great."
  ^
leveldb/util/logging.cc: In function ‘bool leveldb::ConsumeDecimalNumber(leveldb::Slice*, uint64_t*)’:
leveldb/util/logging.cc:58:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           (v == kMaxUint64/10 && delta > kMaxUint64%10)) { // FIXME.SUGAR // BTC issue
                                        ^
leveldb/port/port_posix.cc: In function ‘bool leveldb::port::HasAcceleratedCRC32C()’:
leveldb/port/port_posix.cc:60:15: warning: ‘ecx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   return (ecx & (1 << 20)) != 0; // FIXME.SUGAR // BTC issue
               ^
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')

BTC FULL LOG

$ make -j8 | grep "warning:"
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')
key.cpp: In function ‘int ec_privkey_import_der(const secp256k1_context*, unsigned char*, const unsigned char*, size_t)’:
key.cpp:51:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (end - privkey < lenb) {
                       ^
key.cpp:57:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (end - privkey < len) {
                       ^
key.cpp:71:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (oslen > 32 || end - privkey < oslen) {
                                     ^
ar: `u' modifier ignored since `D' is the default (see `U')
leveldb/util/logging.cc: In function ‘bool leveldb::ConsumeDecimalNumber(leveldb::Slice*, uint64_t*)’:
leveldb/util/logging.cc:58:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           (v == kMaxUint64/10 && delta > kMaxUint64%10)) {
                                        ^
leveldb/port/port_posix.cc: In function ‘bool leveldb::port::HasAcceleratedCRC32C()’:
leveldb/port/port_posix.cc:60:15: warning: ‘ecx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   return (ecx & (1 << 20)) != 0;
               ^
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')

/* comment */

1965b15

2020-02-04 05:40:53 Assuming ancestors of block 9998f536feb26f749ed9198f56f397da08f018de9518674b2ac12a41061612cb have valid signatures.
2020-02-04 05:40:53 Setting nMinimumChainWork=00000000000000000000000000000000000000000000000000000b63a48c5c1e

#51

KezToday at 9:42 PM
Guys, everytime I load the wallet, i need to resync entire chain. Any reason why?

@volbil#8559 right.

it can be caused by node crash during shut down. Blockchain filed get corrupted and it triggers reindex.

@kez#3857 did shut down his Windows10, but Yumekawa didn't hear the signal. so it was forced shut down. so blockdata didn't finalized. he had to reindex again after reboot. i had similar issue on BTC.

2019-12-29 18:08:02 Dumped mempool: 0s to copy, 0s to dump
2020-01-01 12:41:39 

Normal shutdown is like so: Shutdown: done

2020-01-01 13:02:24 Dumped mempool: 5e-06s to copy, 0.004548s to dump
2020-01-01 13:02:24 Shutdown: done

hide testnet launch icon or change icon different style.

I found that some new users have synced testnet for two days

1

ResistancePlatform/resistance-core@a73d694

KotoDevelopers/koto@79f4798

yespower_cache

However, even if you use or introduce CBlockHeader::GetPoWHash() caching may still be desirable as the PoW hash is commonly requested 4 times per block fetched during a node's initial blockchain sync (once during prefetch of block headers, and 3 times more during validation of a fully fetched block).

cryptozeny/sugarchain-v0.16.3#122
cryptozeny/sugarchain-v0.16.3#117

https://github.com/litecoin-project/litecoin/blob/1b6c480754d559db3650b226178d9221ec46b4d2/src/validation.h#L197

safer, but first start up will be bit slower.

cryptozeny/sugarchain-v0.16.3#60

https://github.com/sugarchain-project/sugarchain-detached-sigs/tree/0.16/win
https://github.com/RavenProject/Ravencoin/tree/master/static-builds
litecoin-project/litecoin@c080338

Signing PGP to Binaries (Windows and OSX: --os wx) TODO

cd && \
./gitian-build.sh -j 3 -m 3000 --os wx --detach-sign --no-commit -s cryptozeny 0.16.3.10rc25

Won't work

https://gist.github.com/cryptozeny/3501c77750541208b9dd1a9e9719fc53

I think to buy windows certificate from comodoca

https://github.com/cryptozeny/sugarchain-v0.16.3/blob/2336cc9d3edbb5ad58bfbabefb09a07859919196/test/functional/test_framework/mininode.py#L54

MAGIC_BYTES = {
    "mainnet": b"\xf9\xbe\xb4\xd9",   # mainnet
    "testnet3": b"\x0b\x11\x09\x07",  # testnet3
    "regtest": b"\xfa\xbf\xb5\xda",   # regtest
}

its still in BTC original

cryptozeny/sugarchain-v0.16.3#95

reported by salmaan1234 @Nugetzrul3

When running sugarchain daemon on arm32, the process repeatedly keeps going from the running state to a 'D' state, then for some reason suspends itself
i guess thats basically it

https://youtu.be/WFEEeVcKtaQ

It says its in the R state for like a few secods
Then it switches to D stage
Then it switches to suspeneded

Process state
R - running or runnable (on run queue)
S - interruptible sleep (waiting for an event to complete)
D - uninterruptible sleep (usually IO)
Z - defunct ("zombie") process, terminated but not reaped by its parent
T - stopped by job control signal
t - stopped by debugger during the tracing

    // Extremely large transactions with lots of inputs can cost the network
    // almost as much to process as they cost the sender in fees, because
    // computing signature hashes is O(ninputs*txsize). Limiting transactions
    // to MAX_STANDARD_TX_WEIGHT mitigates CPU exhaustion attacks.

bitcoin/bitcoin#6522

https://github.com/sugarchain-project/sugarchain/blob/master-v0.16.3/src/policy/policy.cpp#L89-L97

https://github.com/sugarchain-project/sugarchain/blob/master-v0.16.3/src/wallet/wallet.cpp#L2991-L2996

src/policy/policy.h:static const unsigned int MAX_STANDARD_TX_WEIGHT = 400000;

its common issue on BTC based blockchain. it will fixed in Schnorr Signature update.

incorrect, but intedned.

estimatesmartfee 6

{
  "errors": [
    "Insufficient data or no feerate found"
  ],
  "blocks": 6
}

@volbil

only WIN32 is different. i tried 3 times, but always different.

strange, in some case, sugarchain-0.16.3-win32-setup-unsigned.exe sha256hash is only changed. (the others OK) need verify.

• 1st
  84633a80534732c73a2011e0783554d5ac0ba8b6ceed65c79c17b3f3dafd252b sugarchain-0.16.3-win32-setup-unsigned.exe

• 2nd
  5c499f90f84fbac8768d74d1bd8d59a670420f9d5ea7a356b39972bce3afd704 sugarchain-0.16.3-win32-setup-unsigned.exe

• 3rd
  a432640eb9247dca98a107350f4e9d741b4da84a3be8359fcba417d44755bc31 sugarchain-0.16.3-win32-setup-unsigned.exe

https://gist.github.com/cryptozeny/3501c77750541208b9dd1a9e9719fc53#gistcomment-3167642

474615a

i made some error, but no error.

litecoin-project/litecoin#616
bitcoin/bitcoin#18066
#51

https://github.com/bitcoin/bitcoin/pull/14027/files

in 0.18

https://twitter.com/zawy3/status/1226951717683593216

zcash/zcash#4021 (comment)

check what fixed.

IBD duration is also affected by how quickly a new node (without peers.dat) finds other nodes, and you can probably speed this up with:

zcash/zcash#4274

Alexander

Time Duration

• Linux32 7min

sugarchain-0.16.3-Linux32$ time ./bin/test_sugarchain 
Running 282 test cases...

*** No errors detected

real	6m57.936s
user	7m3.984s
sys	0m1.436s

• Linux64 2min

$ time ./sugarchain-0.16.3-Linux64/bin/test_sugarchain 
Running 282 test cases...

*** No errors detected

real	2m4.659s
user	2m6.872s
sys	0m2.513s

LTC

• 32

litecoin-0.16.3-L32/bin$ time ./test_litecoin 
Running 278 test cases...

*** No errors detected

real	1m21.478s
user	1m24.015s
sys	0m3.013s

• 64

litecoin-0.16.3/bin$ time ./test_litecoin
Running 278 test cases...

*** No errors detected

real	0m49.017s
user	0m49.116s
sys	0m2.218s

64-Bit is 2x faster than 32-Bit

maybe 32-Bit with -msse2 will improve speed

before -fomit-frame-pointer

Linux32 5min
Linux64 2min

Tested on Real Windows Machine:

Win32 9min
Win64 5min