[ANN] Signatum - New Algorithm - Fair Launch - No Premine - page 487.

mitch8128

newbie

Activity: 57

Merit: 0

Quote from: Shankar94 on July 23, 2017, 10:51:31 PM

Only one month ? Shocked

Hope i get a few coins in mining..
SP mod Helps a lot !! 62 mh/s to 98mh/s Cheesy

any chance i can get some more info on this and where to get it?
bit of a noob over here Undecided

sigt: BNmnPTToDv8ZRAiZBcXZq75UkmcpaYDsdo

TheKingInYellow

sr. member

Activity: 546

Merit: 257

Have you found the Yellow Sign?

Wow!! The network hash just spiked to 900k mh/s!!!

We will run out of PoW in two weeks at this rate!!

Shankar94

full member

Activity: 140

Merit: 100

DeepOnion ♡

Only one month ? Shocked

Hope i get a few coins in mining..
SP mod Helps a lot !! 62 mh/s to 98mh/s Cheesy

TheKingInYellow

sr. member

Activity: 546

Merit: 257

Have you found the Yellow Sign?

Network hashrate growing.. solidly past 400k MH/s and tipping 550k. Now we're chewing through blocks at a rate of 2.5/minute or about 3600/day. That gives us about 1 month of PoW. That's if the hash doesn't continue to grow, like I forsee. SIGT is about to become a rare commodity at this rate.

SunStruck

sr. member

Activity: 676

Merit: 250

Meh ... hashbag.cc ninja bumped to 2% fee , time to switch pools.

wavelengthsf

full member

Activity: 658

Merit: 118

Quote from: signatum on July 23, 2017, 07:27:17 PM

Quote from: maxmad_x on July 23, 2017, 07:18:30 PM

Quote from: maxmad_x on July 23, 2017, 07:10:27 PM

Can anyone please share their nodes? I am still unable to get a lock on any of the nodes. So wallet is out of sync
Any solution to

Code:

socket recv error 10054

some more information on this
WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

So its a remote server problem ! Nodes are not accepting connections or what?

Try adding these nodes to your config

Code:

addnode=54.175.225.242
addnode=122.129.64.13
addnode=122.129.64.14
addnode=122.129.64.15
addnode=122.129.64.16
addnode=203.128.6.219
addnode=104.154.193.236
addnode=104.198.232.113
addnode=104.199.11.56
addnode=130.211.127.202
addnode=35.184.49.142
addnode=35.189.14.132
addnode=35.185.18.85
addnode=35.184.121.184

Thanks, this fixed the same issue on my client.

TheKingInYellow

sr. member

Activity: 546

Merit: 257

Have you found the Yellow Sign?

Quote from: strannik951159 on July 23, 2017, 07:42:07 PM

[2017-07-24 03:41:33] skunk block 8197, diff 5432.445

Feel blessed to have mined what I did! Looks like the Megaminers are smelling the money here.

strannik951159

member

Activity: 112

Merit: 10

📌[ANN]📌👍👍👍

[2017-07-24 03:41:33] skunk block 8197, diff 5432.445

signatum

newbie

Activity: 59

Merit: 0

Quote from: maxmad_x on July 23, 2017, 07:18:30 PM

Quote from: maxmad_x on July 23, 2017, 07:10:27 PM

Can anyone please share their nodes? I am still unable to get a lock on any of the nodes. So wallet is out of sync
Any solution to

Code:

socket recv error 10054

some more information on this
WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

So its a remote server problem ! Nodes are not accepting connections or what?

Try adding these nodes to your config

Code:

addnode=54.175.225.242
addnode=122.129.64.13
addnode=122.129.64.14
addnode=122.129.64.15
addnode=122.129.64.16
addnode=203.128.6.219
addnode=104.154.193.236
addnode=104.198.232.113
addnode=104.199.11.56
addnode=130.211.127.202
addnode=35.184.49.142
addnode=35.189.14.132
addnode=35.185.18.85
addnode=35.184.121.184

maxmad_x

sr. member

Activity: 546

Merit: 250

It takes a lot to build but not much to lose

Quote from: maxmad_x on July 23, 2017, 07:10:27 PM

Can anyone please share their nodes? I am still unable to get a lock on any of the nodes. So wallet is out of sync
Any solution to

Code:

socket recv error 10054

some more information on this
WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

So its a remote server problem ! Nodes are not accepting connections or what?

enkayz

full member

Activity: 298

Merit: 100

hashbag.cc

Quote from: TheKingInYellow on July 23, 2017, 05:21:59 PM

Quote from: OXUS on July 23, 2017, 05:19:03 PM

Dev is open to suggestions on telegram , i talked to him about keeping the POW phase little longer

I guess I should have been more clear: I'm ok with SIGT going full PoS at block 100k, it's a rock solid roadmap and transparent to anyone interested in that stuff. I more mean I'd love to see this algorithm be let loose into the wild and see more coins using it Wink

We're up to 400,000 MH/s for the network, this is getting ridiculous!

Can you point me to the roadmap link or whitepaper?

maxmad_x

sr. member

Activity: 546

Merit: 250

It takes a lot to build but not much to lose

Can anyone please share their nodes? I am still unable to get a lock on any of the nodes. So wallet is out of sync
Any solution to

Code:

socket recv error 10054

SunStruck

sr. member

Activity: 676

Merit: 250

Damn , hoped I can mine covert a bit longer Roll Eyes

rauderce

newbie

Activity: 53

Merit: 0

more than 10 btc has been traded. Difficulty has been steadily increasing

enkayz

full member

Activity: 298

Merit: 100

hashbag.cc

hashbag.cc now paying out each 2 hours for your hashing convenience!

in regard to block time it looks like it's closer to 1 minute, not sure if this was intentional but the PoW phase will be over in a couple of weeks at this rate, so you better get in fast, lol

TheKingInYellow

sr. member

Activity: 546

Merit: 257

Have you found the Yellow Sign?

850 sat with HUGE buy walls. this is a great first day of trading

Seems like Mr market in China is hearing about SIGT.

makrove

newbie

Activity: 3

Merit: 0

If I'm mining independent to know how long the block arrives --gtx 1080 x 3

ItaCraft

member

Activity: 138

Merit: 10

Quote from: gargouri20011 on July 23, 2017, 05:55:56 PM

Quote from: TheKingInYellow on July 23, 2017, 05:21:59 PM

Quote from: OXUS on July 23, 2017, 05:19:03 PM

Dev is open to suggestions on telegram , i talked to him about keeping the POW phase little longer

I guess I should have been more clear: I'm ok with SIGT going full PoS at block 100k, it's a rock solid roadmap and transparent to anyone interested in that stuff. I more mean I'd love to see this algorithm be let loose into the wild and see more coins using it Wink

We're up to 400,000 MH/s for the network, this is getting ridiculous!

"netmhashps" : 215170.40954446,

how did u calculate 400 mhash it is 215 Huh

Its due the DGW3 Difficult algo, for a exemple, see this https://www.coinwarz.com/network-hashrate-charts/dash-network-hashrate-chart

natan069

full member

Activity: 198

Merit: 100

SP ccminer private version here
Doing almost 16mhs on 1060 3gb
keep on mining.

strannik951159

member

Activity: 112

Merit: 10

📌[ANN]📌👍👍👍

Quote from: gargouri20011 on July 23, 2017, 05:55:56 PM

Quote from: TheKingInYellow on July 23, 2017, 05:21:59 PM

Quote from: OXUS on July 23, 2017, 05:19:03 PM

Dev is open to suggestions on telegram , i talked to him about keeping the POW phase little longer

I guess I should have been more clear: I'm ok with SIGT going full PoS at block 100k, it's a rock solid roadmap and transparent to anyone interested in that stuff. I more mean I'd love to see this algorithm be let loose into the wild and see more coins using it Wink

We're up to 400,000 MH/s for the network, this is getting ridiculous!

"netmhashps" : 215170.40954446,

how did u calculate 400 mhash it is 215 Huh

skunk block 8097, diff 4136.224
Net Hash: 481,391.88 MH/s

Topic: [ANN] Signatum - New Algorithm - Fair Launch - No Premine - page 487. (Read 823878 times)