Pages:
Author

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 15. (Read 284948 times)

legendary
Activity: 2646
Merit: 1722
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF
Lets put it to a vote to switch algo then - the logical choice being SHA-256 like Bitcoin and Peercoin. I think I would actually vote yes on that.

Oh, and NOMP server has finally accepted the first DCrypt block!

Code:
2014-10-27 19:55:45 [Pool]      [slimcoin] (Thread 1) Submitted Block using submitblock successfully to daemon instance(s)
2014-10-27 19:55:45 [Pool]      [slimcoin] (Thread 1) Block found: 00000002762cab5802109aa37cf8c5f08c77cde1611a017c3e3e130eea352695

Excellent news and great work!

Dcrypt algo and CPU mining is OK with me! Someone will eventually find a way to mine it with a GPU or ASIC + CPU / RAM combo and cpu coin pools will always have problems from botnets obviously.

Anyway, herewith a single CPU instance at RunAbove - http://labs.runabove.com/power8/ - Not totally sure on the billing in comparison to other cloud server providers, but those are certainly some powerful core(s).



If you follow my set-up guide from this thread remember to use screen.

See: https://bitcointalksearch.org/topic/m.9330074

Code:
screen

before you start mining using:

Code:
./minerd -a dcrypt -o stratum+tcp://www.slimcoin.club:41680 -u YOUR SLIMCOIN WALLET ADDRESS -p x --scantime 15 --retries -1 -t 1


You can then (press and hold) CTRL + A + D to get out of the screen session. Then type exit and press enter to close the terminal, although continue mining Slimcoin.

...

If you log back in to the terminal type: screen -r and Enter to check that your still mining Slimcoin.

If you need to stop mining Slimcoin type: sudo killall minerd and press enter.

To restart mining type / repeat only steps:

Code:
cd slimminer

Code:
screen

Code:
./minerd -a dcrypt -o stratum+tcp://www.slimcoin.club:41680 -u YOUR SLIMCOIN WALLET ADDRESS -p x --scantime 15 --retries -1 -t 1
newbie
Activity: 21
Merit: 0
Lets put it to a vote to switch algo then - the logical choice being SHA-256 like Bitcoin and Peercoin. I think I would actually vote yes on that.

Hmm I'm not quite for SHA-256 since I like the idea of SLM being a gpu/asic-resistant coin.
+1, I think the idea of using dcrypt is to discourage intensive mining, partly since the point of Slimcoin is to require less 'wasted' power in mining by encouraging proof-of-burn to be more significant than proof-of-work. I would favor an algorithm that's going to be hard to accelerate, for that reason.

(PS -- I downloaded the 0.3.2.1 Windows build from the Git releases, and it was crashing again like the old wallet did. I've had to go back to 0.3.2.0 for the time being. Sad )
hero member
Activity: 673
Merit: 500
Lets put it to a vote to switch algo then - the logical choice being SHA-256 like Bitcoin and Peercoin. I think I would actually vote yes on that.

Oh, and NOMP server has finally accepted the first DCrypt block!

Code:
2014-10-27 19:55:45 [Pool]      [slimcoin] (Thread 1) Submitted Block using submitblock successfully to daemon instance(s)
2014-10-27 19:55:45 [Pool]      [slimcoin] (Thread 1) Block found: 00000002762cab5802109aa37cf8c5f08c77cde1611a017c3e3e130eea352695

Excellent news and great work!
full member
Activity: 222
Merit: 103
Oh, and NOMP server has finally accepted the first DCrypt block!

Thanks a123, trying once again!
member
Activity: 98
Merit: 10
Lets put it to a vote to switch algo then - the logical choice being SHA-256 like Bitcoin and Peercoin. I think I would actually vote yes on that.

Hmm I'm not quite for SHA-256 since I like the idea of SLM being a gpu/asic-resistant coin.

Oh, and NOMP server has finally accepted the first DCrypt block!

Code:
2014-10-27 19:55:45 [Pool]      [slimcoin] (Thread 1) Submitted Block using submitblock successfully to daemon instance(s)
2014-10-27 19:55:45 [Pool]      [slimcoin] (Thread 1) Block found: 00000002762cab5802109aa37cf8c5f08c77cde1611a017c3e3e130eea352695
legendary
Activity: 2646
Merit: 1722
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

...

the new coin primer- mentioned is a prime based one, and those are really hard to accelerate.

I'm beginning to think dcrypt is no longer a CPU-only algorithm, judging by the concentration of hashpower of the past few days in a few addresses. we might need to come up with a new one hmm. as someone mentioned recently, the assumption of the unbounded scratch space is not true (i.e. you only need a small fixed amount of memory if you are willing to make certain trade offs), and it's operation intensive rather than memory intensive.

Gapcoin helps to find new Prime Gaps and is similar to Primecoin in many respects. Both projects are interesting and unique from a mathematical and scientific perspective.

I'm currently mining Gapcoin and Slimcoin (and sometimes some Primecoin too).

Slimcoin is mostly interesting from an economic perspective in terms of crypto innovation. The Slimcoin developer did a lot of really 'smart' things with this coin to make it different and it remains so.

If you look at Slimcoin's posts - he perhaps didn't really want this coin to have a pool and the choice of the unique dcrypt algo has certainly helped and somewhat hindered this coins progress in this regard. Other technical oversights have not helped with the situation or with Slimcoins adoption.

Lets put it to a vote to switch algo then - the logical choice being SHA-256 like Bitcoin and Peercoin. I think I would actually vote yes on that.
member
Activity: 98
Merit: 10

Dead ? Thank primer-, after you gone price rise from 180 sat to 10k sat. Diff rise from 0.03 to 0.3.
All thanks to you. Please feel free to leave forever, don't ever come back. Wink


Good luck with the new clueless dev, idiot. Smiley

Good luck with your self illusion, idiot. Wink

Well he's not technically wrong xD



the new coin primer- mentioned is a prime based one, and those are really hard to accelerate.

I'm beginning to think dcrypt is no longer a CPU-only algorithm, judging by the concentration of hashpower of the past few days in a few addresses. we might need to come up with a new one hmm. as someone mentioned recently, the assumption of the unbounded scratch space is not true (i.e. you only need a small fixed amount of memory if you are willing to make certain trade offs), and it's operation intensive rather than memory intensive.
hero member
Activity: 938
Merit: 1000

Dead ? Thank primer-, after you gone price rise from 180 sat to 10k sat. Diff rise from 0.03 to 0.3.
All thanks to you. Please feel free to leave forever, don't ever come back. Wink


Good luck with the new clueless dev, idiot. Smiley

Good luck with your self illusion, idiot. Wink
legendary
Activity: 1092
Merit: 1000

Dead ? Thank primer-, after you gone price rise from 180 sat to 10k sat. Diff rise from 0.03 to 0.3.
All thanks to you. Please feel free to leave forever, don't ever come back. Wink


Good luck with the new clueless dev, idiot. Smiley
hero member
Activity: 938
Merit: 1000

Dead ? Thank primer-, after you gone price rise from 180 sat to 10k sat. Diff rise from 0.03 to 0.3.
All thanks to you. Please feel free to leave forever, don't ever come back. Wink
member
Activity: 98
Merit: 10
If anyone is interested in taking a look at the submitblock issue,

Code:
slimcoind submitblock 01000000f2d59cd21920d6c06c3a4a4e5665ccc791a3ef412680f82fa33eb28e00000000ab110d0b1946579cf081ceade6fdca70c37ee09b0559c76ef24544d5a162c12b92ff4d54c85e031d261c23000101000000010000000000000000000000000000000000000000000000000000000000000000ffffffff27035c1502062f503253482f04a2ff4d5408080000000000000d0d2f6e6f64655374726174756d2f000000000338a87e00000000001976a91483c0525511cf0f49325f8d9634781efa4897d1ea88acdc4a0100000000001976a914b97278df80bbc7d0f4370356b990dda77753fe1d88acdc4a0100000000001976a914ce572bb0049ccba44d820181ba1b922badcaa41988ac00000000

will give

Code:
******* exception encountered *******
./slimcoind(_Z13LogStackTracev+0x3c)[0x5fa71c]
./slimcoind(_ZN11CDataStream4readEPci+0xe7)[0x520647]
./slimcoind[0x547aa7]
./slimcoind(_Z16Unserialize_implI11CDataStream5CTxInSaIS1_EEvRT_RSt6vectorIT0_T1_EiiRKN5boost17integral_constantIbLb0EEE+0x185)[0x578505]
./slimcoind[0x54c991]
./slimcoind(_Z16Unserialize_implI11CDataStream12CTransactionSaIS1_EEvRT_RSt6vectorIT0_T1_EiiRKN5boost17integral_constantIbLb0EEE+0x138)[0x57dcb8]
./slimcoind(_ZN6CBlock11UnserializeI11CDataStreamEEvRT_ii+0x23f)[0x57e02f]
./slimcoind(_Z11submitblockRKSt6vectorIN11json_spirit10Value_implINS0_13Config_vectorISsEEEESaIS4_EEb+0x48e)[0x5b567e]
./slimcoind(_ZNK9CRPCTable7executeERKSsRKSt6vectorIN11json_spirit10Value_implINS3_13Config_vectorISsEEEESaIS7_EE+0x14d)[0x5b15cd]
./slimcoind(_Z16ThreadRPCServer2Pv+0x1905)[0x5b8655]
./slimcoind(_Z15ThreadRPCServerPv+0xa2)[0x5ba182]
/lib64/libpthread.so.0(+0x7df3)[0x7f3f178b3df3]
/lib64/libc.so.6(clone+0x6d)[0x7f3f172df01d]

This is during the Serialization to CBlock.
hero member
Activity: 673
Merit: 500
I've taken the NOMP pool down - I've confirmed that there's a submitblock issue, slimcoind crashes without any error log, every time a valid submitblock is submitted.

Will be working on fixing it on the Slimcoin client side, suspect it's a block header mismatch issue: no burn fields in the block header submitted by NOMP, and it doesn't seem that Slimcoin's block parsing routine handles this. Will investigate further and report back!

NOMP cannot use getwork to receive jobs so submitblock must be fixed, but think MPOS can receive getwork jobs so that might mean suprnova's one might work.

Isn't MPOS just the front end?  I'm guessing ocminer has added dcrypt to stratum, and it may actually be working, but his server is refusing connections at the moment.  If we can get him to fix it, I will throw some big hashpower at it for a couple hours to see if we can find a a block. 
member
Activity: 98
Merit: 10
I've taken the NOMP pool down - I've confirmed that there's a submitblock issue, slimcoind crashes without any error log, every time a valid submitblock is submitted.

Will be working on fixing it on the Slimcoin client side, suspect it's a block header mismatch issue: no burn fields in the block header submitted by NOMP, and it doesn't seem that Slimcoin's block parsing routine handles this. Will investigate further and report back!

NOMP cannot use getwork to request for jobs so submitblock must be fixed, but think MPOS can request getwork so that might mean suprnova's one might work out?
hero member
Activity: 673
Merit: 500
full member
Activity: 222
Merit: 103
Left 2 colocation servers on both pools (one for one) - tomorrow will see if something gonna change
hero member
Activity: 938
Merit: 1000
I get a lot of disconnections from suprnova pool Sad
Less than 50% acceptance shares.


very strange... 100% accepted at the moment.

I was getting 100% at first but after 10 hours only 50%. No idea what happens.
full member
Activity: 222
Merit: 103
I get a lot of disconnections from suprnova pool Sad
Less than 50% acceptance shares.


very strange... 100% accepted at the moment.
hero member
Activity: 938
Merit: 1000
Just added 2 more workers @ SuprNova pool. Looking forward to find a block $-)

I get a lot of disconnections from suprnova pool Sad
Less than 50% acceptance shares.
full member
Activity: 222
Merit: 103
Just added 2 more workers @ SuprNova pool. Looking forward to find a block $-)
Pages:
Jump to: