[SUSU][SHA256] Susucoin - Securing free speech

[cvm]

Windows wallet seems to be working fine, and I have put it back on the website for download. The segwit addresses aren't working well yet due to lack of witnesses. Please use the non-segwit addresses for now.

Ok. There seems to be a problem with windows wallets receiving coins at the moment. Working on fixing this.

linux daemon also not compiling from source, autogen.sh

What is your distro? Susucoin will compile easily on newer versions of Ubuntu and Debian if you follow these instructions:
https://github.com/susucoin-project/susucoin/blob/master/doc/build-unix.md

ubuntu 16.04

Code:

some@ubuntu:~/work/susucoin$ ./autogen.sh
aclocal: warning: couldn't open directory 'build-aux/m4': No such file or directory
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build-aux/m4'.
libtoolize: copying file 'build-aux/m4/libtool.m4'
libtoolize: copying file 'build-aux/m4/ltoptions.m4'
libtoolize: copying file 'build-aux/m4/ltsugar.m4'
libtoolize: copying file 'build-aux/m4/ltversion.m4'
libtoolize: copying file 'build-aux/m4/lt~obsolete.m4'
configure.ac:45: installing 'build-aux/compile'
configure.ac:45: installing 'build-aux/config.guess'
configure.ac:45: installing 'build-aux/config.sub'
configure.ac:28: installing 'build-aux/install-sh'
configure.ac:28: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build-aux/m4'.
libtoolize: copying file 'build-aux/m4/libtool.m4'
libtoolize: copying file 'build-aux/m4/ltoptions.m4'
libtoolize: copying file 'build-aux/m4/ltsugar.m4'
libtoolize: copying file 'build-aux/m4/ltversion.m4'
libtoolize: copying file 'build-aux/m4/lt~obsolete.m4'
configure.ac:10: installing 'build-aux/compile'
configure.ac:5: installing 'build-aux/config.guess'
configure.ac:5: installing 'build-aux/config.sub'
configure.ac:9: installing 'build-aux/install-sh'
configure.ac:9: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build-aux/m4'.
libtoolize: copying file 'build-aux/m4/libtool.m4'
libtoolize: copying file 'build-aux/m4/ltoptions.m4'
libtoolize: copying file 'build-aux/m4/ltsugar.m4'
libtoolize: copying file 'build-aux/m4/ltversion.m4'
libtoolize: copying file 'build-aux/m4/lt~obsolete.m4'
autoheader: cannot rename /tmp/arka9cUA/ah8SIFDP/config.hin as src/config/bitcoin-config.h.in: No such file or directory
autoreconf: /usr/bin/autoheader failed with exit status: 1

I guess this is just a matter of creating an empty m4 directory. Can you verify

Code:

m4$ ll
./
../
ax_boost_base.m4
ax_boost_chrono.m4
ax_boost_filesystem.m4
ax_boost_program_options.m4
ax_boost_system.m4
ax_boost_thread.m4
ax_boost_unit_test_framework.m4
ax_check_compile_flag.m4
ax_check_link_flag.m4
ax_check_preproc_flag.m4
ax_cxx_compile_stdcxx.m4
ax_gcc_func_attribute.m4
ax_pthread.m4
bitcoin_find_bdb48.m4
bitcoin_qt.m4
bitcoin_subdir_to_include.m4
l_atomic.m4
libtool.m4
obsolete.m4
ltoptions.m4
ltsugar.m4
ltversion.m4

[1713284718]

1713284718

[1713284718]

1713284718

[1713284718]

1713284718

[AltcoinCash]

What's this, a no fuss coin?

[TheRaster]

also at the mining site, it shows its a  x11 coin, i thought it was scrypt...can you tell me which one it is..

im the opp of that site we would like to know too.

scrypt blocks get rejected. i have found some x11 in there code so was testing.

even solo dont play well 5 blocks 0 in wallet

Code:

Solo info
Summary of runtime statistics:

 [2018-06-10 18:11:13] Started at [2018-06-10 17:43:04]
 [2018-06-10 18:11:13] Pool: http://xxx.xxx.xxx.xxx:9432/
 [2018-06-10 18:11:13] Runtime: 0 hrs : 28 mins : 8 secs
 [2018-06-10 18:11:13] Average hashrate: 0.8 Mhash/s
 [2018-06-10 18:11:13] Solved blocks: 5
 [2018-06-10 18:11:13] Best share difficulty: 207K
 [2018-06-10 18:11:13] Share submissions: 4
 [2018-06-10 18:11:13] Accepted shares: 4
 [2018-06-10 18:11:13] Rejected shares: 0
 [2018-06-10 18:11:13] Accepted difficulty shares: 30984
 [2018-06-10 18:11:13] Rejected difficulty shares: 0
 [2018-06-10 18:11:13] Reject ratio: 0.0%
 [2018-06-10 18:11:13] Hardware errors: 0
 [2018-06-10 18:11:13] Utility (accepted shares / min): 0.14/min
 [2018-06-10 18:11:13] Work Utility (diff1 shares solved / min): 0.18/min

 [2018-06-10 18:11:13] Stale submissions discarded due to new blocks: 1
 [2018-06-10 18:11:13] Unable to get work from server occasions: 0
 [2018-06-10 18:11:13] Work items generated locally: 812
 [2018-06-10 18:11:13] Submitting work remotely delay occasions: 1
 [2018-06-10 18:11:13] New blocks detected on network: 17

[index932]

Dev, finding all orphan blocks only. Please advise.

[Susucoin]

I am receiving many complaints about pools being unable to mine Susucoin. Was working on debugging it last night [I am based in Asia], but fell asleep before I could finish debugging. Will work on getting this problem resolved today. Sorry for any delay or disappointment in your mining pools.

[Susucoin]

This morning with a fresh mind, I think I found the problem with the mining pools. There was a typo in my seed node's susucoin.conf file. The port number was set incorrectly, overriding the default of 9432. It is set correctly now, and in theory should work correctly with pools now.
Please let me know if there are still any problems with mining. Sorry for all the trouble yesterday.

[index932]

This morning with a fresh mind, I think I found the problem with the mining pools. There was a typo in my seed node's susucoin.conf file. The port number was set incorrectly, overriding the default of 9432. It is set correctly now, and in theory should work correctly with pools now.
Please let me know if there are still any problems with mining. Sorry for all the trouble yesterday.

Do we need to recompile the code to get this fixed or just a restart of the daemon would do? Please let us know what do we need to do from the pool end?  We are getting all orphan blocks as of now...

[AmoreJaz]

What's this, a no fuss coin?

ill be checking if the claimed partnership is true. or this is just another coin trying to survive from very few miners of this coin?

[Susucoin]

This morning with a fresh mind, I think I found the problem with the mining pools. There was a typo in my seed node's susucoin.conf file. The port number was set incorrectly, overriding the default of 9432. It is set correctly now, and in theory should work correctly with pools now.
Please let me know if there are still any problems with mining. Sorry for all the trouble yesterday.

Do we need to recompile the code to get this fixed or just a restart of the daemon would do? Please let us know what do we need to do from the pool end?  We are getting all orphan blocks as of now...

Restarting the daemon should just work.

What's this, a no fuss coin?

ill be checking if the claimed partnership is true. or this is just another coin trying to survive from very few miners of this coin?

Sure thing. I am not hyping the coin as of now because I would prefer to work out any bugs in the basic systems before making any announcements.
If all goes well, I will put out the press release on Friday.

Cheers.

[index932]

This morning with a fresh mind, I think I found the problem with the mining pools. There was a typo in my seed node's susucoin.conf file. The port number was set incorrectly, overriding the default of 9432. It is set correctly now, and in theory should work correctly with pools now.
Please let me know if there are still any problems with mining. Sorry for all the trouble yesterday.

Do we need to recompile the code to get this fixed or just a restart of the daemon would do? Please let us know what do we need to do from the pool end?  We are getting all orphan blocks as of now...

Restarting the daemon should just work.

What's this, a no fuss coin?

ill be checking if the claimed partnership is true. or this is just another coin trying to survive from very few miners of this coin?

Sure thing. I am not hyping the coin as of now because I would prefer to work out any bugs in the basic systems before making any announcements.
If all goes well, I will put out the press release on Friday.

Cheers.

Dev, the restart of the daemon did not work. I still get all orphan blocks only! Check my pool here: https://weekendpool.org

[cvm]

Susucoin temporally disabled on CVMpool.pw

https://screenshotscdn.firefoxusercontent.com/images/d7ba583a-f33a-4d9b-9820-c17c712194c6.png

all blocks do not matured
https://screenshotscdn.firefoxusercontent.com/images/c9dda73c-267a-4eb1-9e5c-6889f663f2aa.png

[GrampaHenry]

So, I'm assuming the block are lost and I will not be paid for them?  Will stop mining until this is fixed. 

[merridaa]

seems a lot to be fixed before this announcement update project, there are many complaints that happened even before the project launcing, I'm a bit worried about its development, and yes, the concept is quite strange to me

[Susucoin]

Ive been thinking about this all day. There are many orphaned blocks from miners in pools. It seems to be a network latency issue. The target spacing is currently set to 2 minutes. If the target spacing is changed to 5 minutes, it should fix the latency issue with pools not syncing properly within the 2 minute target space. Tomorrow I will setup some more seed nodes around the world, and update the source code for a 5 minute target spacing. I have made an issue on the susucoin-project github for this.
https://github.com/susucoin-project/susucoin/issues/1

[index932]

Ive been thinking about this all day. There are many orphaned blocks from miners in pools. It seems to be a network latency issue. The target spacing is currently set to 2 minutes. If the target spacing is changed to 5 minutes, it should fix the latency issue with pools not syncing properly within the 2 minute target space. Tomorrow I will setup some more seed nodes around the world, and update the source code for a 5 minute target spacing. I have made an issue on the susucoin-project github for this.
https://github.com/susucoin-project/susucoin/issues/1

Okay. Please update once ready!

[Susucoin]

Instead of hard forking to a slower target spacing, I decided to build more full nodes on vps around the world. With improved latency we should have better connectivity and in theory that should help us prevent seeing so many orphans while pool mining.
I have setup a discord server if anybody wants to join and ask me questions.
https://discord.gg/7QQZh27
My user name is: susucoin#4239

[AmoreJaz]

What's this, a no fuss coin?

ill be checking if the claimed partnership is true. or this is just another coin trying to survive from very few miners of this coin?

Sure thing. I am not hyping the coin as of now because I would prefer to work out any bugs in the basic systems before making any announcements.
If all goes well, I will put out the press release on Friday.

Cheers.

yeah, better do that rather than seeing one-liner posts stating great, nice, awesome etc... with no basis at all. to be honest, the name of your coin sounds weird

[Susucoin]

Due to a large amount of the initial blocks being orphaned due to a bug in the susucoin core wallet, I am planning to reset the susucoin genesis block and start over. I will pre-announce the start of mining here after testing is complete. Sorry for the inconvenience, but I think this is the best way to proceed for the best long-term development and maintenance of susucoin.

[Susucoin]

We will be restarting susucoin tentatively this coming weekend with the sha256 algorithm. New setup is currently undergoing comprehensive testing to make sure pool mining will work correctly without hiccups.

[Susucoin]

Susucoin will be restarted with the SHA256 algorithm on Sunday June 24 2018 @ 14:00 GMT.
The compiled wallets and source code will be made public at that time.