Latest posts of: eeX

https should be implemented last week, but attack had all of our free time.
But it will be ready till March, for sure.

Quote from: kostepanych2 on February 10, 2018, 11:09:22 AM

After switching to BUILD #39 I've found many blocks:

Code:

13:37:43.055664 INFO ;-) Found block for difficulty: 4764933
13:38:21.040039 INFO [5.9.84.141:33711 OUT] Sync data returned unknown top block
: 380671 -> 380672 [1 blocks (0 days) behind]
13:38:21.040039 INFO SYNCHRONIZATION started
13:38:21.321289 INFO >->-> BLOCK ADDED AS ALTERNATIVE ON HEIGHT 380671

But balance in my wallet not changed...

Why???

Should I delete Roaming/sld dir and resync?

Seems you lost your block.
Another solution - restart wallet app.

But you still can be at wrong chain.
So yes, delete all chain data and resync it from scratch.

Hi guys!

Attack mitigated and terminated within 12 hours.
Code fork @ block #377777 was implemented successfully.

No rollback is planned.

Hallelujah!!! [means Zaebis']

seems we will not be listed this months.

Quote from: vanhellzing on February 07, 2018, 03:05:14 PM

Compiling on Linux...got error: "...src/CryptoNoteCore/SwappedMap.h:186:3: error: «cout» is not a member of «std»"

Adding "#include <iostream>" into SwappedMap.h solved the problem

Thanks!!
What linux version exactly?

BUILD #39 is ready to use and must be installed ASAP.

https://bitcointalk.org/index.php?topic=2332011.msg23717891#msg23717891

BUILD #39 already released and now in test phase.

Quote from: Jayjay04 on February 06, 2018, 09:01:12 PM

when is the new version gonna be available ?!

As soon as we choose Fork starting block.
This value will be hardcoded in the next build of Soldo...............

Quote from: httpb on February 06, 2018, 06:29:46 PM

How would people know about the fork? Will the daemon complain or not work after the hard fork?

Can't tell you really.
Most of the people will not see any changes.

But guys who will try to attack soldo network will have their block unconfirmed.

Exchange alive?
Or really hacked and assets lost? Huh

Ok, seems start @ 400K is preferable.

Hello guys,

we have to implement code fork to prevent low difficulty attacks.

The problem is all nodes must be update before hour X.

So - when to start fork - at block 400R or earlier, at 375K???

And third one already!!!

Hello again,

we have the second investor!!!

Quote from: Jegu.Samana on February 05, 2018, 05:33:21 AM

Quote from: awmyhr on February 03, 2018, 11:28:40 PM

With 7 threads I'm getting about 2.30 KH/s! (I didn't run 8 threads cuz my boy is using one core for Minecraft, lol...)

results are really impressive! I can provide two values which were collected by using poor guys hardware:

Xeon E5 1603 v3 (original) - 0.62 KH/s
Xeon E5 2637 V3 ES QEYT (default overclocking in bios) - 1.08 KH/s

BTW I was able to catch 1000 SLD block by using Xeon E5 1603 v3 Wink

Seems we need collect all benchmarking data together and publish at first page...

To wait or not to wait, the question is.........

Quote from: mkilla on February 03, 2018, 07:08:12 PM

What does the Locked Amount represent?

Exactly what you see - you have a coins in the wallet but can't use it until hour X.

In any case thanks a lot for you benchmarking contribute to Soldo mining stats!!!

Quote from: Jegu.Samana on February 02, 2018, 03:47:37 PM

Quote from: eeX on January 31, 2018, 04:25:25 PM

AWS m5.24xlarge EC2 instance @ OREGON with 96 cores will cost you about 4.6 USD/hour.

May you suggest how to calculate thread number. Does your miner needs 2MB L3 cache per thread?

I have tried m4.16xlarge with 64 cores for 1 hour. Best hash ratio that i have seen was 6.2 khs. I was able to reach this hash ratio by using 45 treads. I had two xeons with hyperthreading enabled and 90 MB of L3 in total. So it shows that I'm right according assigning 2 MB per thread.

yes, you are right!
and 6.2 KH/s seems very impresive.

I suppose you should get about 20 SLD during this hour.
If I'm correct, SLD should cost more than USD 0.25 to mining be profitable renting AWS....
At least now....