[ANN] [XSL] Solo - A secure, private, censorship resistant cryptocurrency

[Solo-Project]

We are now on the following coin indexing sites:
https://coinpaprika.com/coin/xsl-solo/
https://delta.app/en/crypto/xsl/solo

[1713486738]

1713486738

[1713486738]

1713486738

[1713486738]

1713486738

[Solo-Project]

We are performing a hard fork at block 440001 (Thursday May 30.2019) to v1.0.4.4. This is a mandatory upgrade that will further reduce difficulty variance and improve network stability. The changes have been simulated and tested for the last two weeks, the benefits warrant a hard fork.

v1.0.4.4
-Update to latest LWMA1 algorithm
-Inclusion of optional optional hashrate adjustment for statistically significant changes in hashrate
-Remove obsolete dependencies
-Re-enable blockchain import for pop blocks functionality
-Remove unnecessary checkpoints

Miners and service providers should upgrade as soon as possible to prevent a break in service.

The most recent binaries are linked below and the main branch in source has been updated.

Windows ( https://www.minesolo.com/release/solo-latest-win64.zip )
Windows NO AES ( https://www.minesolo.com/release/solo-latest-win64-NO_AES.zip )
Linux ( https://www.minesolo.com/release/solo-latest-linux64.tar.gz )
Source ( https://gitlab.com/solo-project/solo )

Changes in the code require a fixed difficulty for the difficulty window. This will be set at 25mm for blocks 440001-440401. Nethash changes by the minute and Solo historically experiences a short drop in hashrate after an upgrade. The fixed difficulty is a conservative estimate based on a historical range, but could result in in block times significantly above or below the 20 second target while working through the window. Following the window, block times will normalize to 20 seconds over the course of several hours.

[casper77]

We are performing a hard fork at block 440001 (Thursday May 30.2019) to v1.0.4.4. This is a mandatory upgrade that will further reduce difficulty variance and improve network stability. The changes have been simulated and tested for the last two weeks, the benefits warrant a hard fork.

v1.0.4.4
-Update to latest LWMA1 algorithm
-Inclusion of optional optional hashrate adjustment for statistically significant changes in hashrate
-Remove obsolete dependencies
-Re-enable blockchain import for pop blocks functionality
-Remove unnecessary checkpoints

Miners and service providers should upgrade as soon as possible to prevent a break in service.

The most recent binaries are linked below and the main branch in source has been updated.

Windows ( https://www.minesolo.com/release/solo-latest-win64.zip )
Windows NO AES ( https://www.minesolo.com/release/solo-latest-win64-NO_AES.zip )
Linux ( https://www.minesolo.com/release/solo-latest-linux64.tar.gz )
Source ( https://gitlab.com/solo-project/solo )

Changes in the code require a fixed difficulty for the difficulty window. This will be set at 25mm for blocks 440001-440401. Nethash changes by the minute and Solo historically experiences a short drop in hashrate after an upgrade. The fixed difficulty is a conservative estimate based on a historical range, but could result in in block times significantly above or below the 20 second target while working through the window. Following the window, block times will normalize to 20 seconds over the course of several hours.

strange things
why my balance became less after update ?

[Solo-Project]

strange things
why my balance became less after update ?

You were possibly mining on a fork - one thing that you can try is to rescan your wallet from block 0 in solo-wallet-cli:

set refresh-from-block-height 0
rescan_bc

[casper77]

strange things
why my balance became less after update ?

You were possibly mining on a fork - one thing that you can try is this to rescan your wallet from block 0:

set refresh-from-block-height 0
rescan_bc

the same balance after that - lesser than before update
should we update before 30 may or nevermind ?

[Solo-Project]

strange things
why my balance became less after update ?

You were possibly mining on a fork - one thing that you can try is this to rescan your wallet from block 0:

set refresh-from-block-height 0
rescan_bc

the same balance after that - lesser than before update
should we update before 30 may or nevermind ?

The fork is still scheduled and will be at block 440001

Height: 416876/416876 (100.0%) on mainnet, mining at 6.42 kH/s, net hash 2.02 MH/s, v17 (next fork in 5.4 days), up to date, 16(out)+0(in) connections, uptime 0d 12h 6m 39s

Do you happen to have the block hash of any blocks you mined and aren't seeing in the wallet?  Sounds likely to me that you were on an alt_chain and not the main chain.  Are you currently synced to the same block as on the block explorer?

Drop in the discord some time - usually somebody around to help

http://discord.minesolo.com/

[cryptomaxsun]

on the exchange cratex.io daemon shows a different height, the deposits do not reach.
I wrote them a ticket.

I have a daemon on the new version periodically writes:

Code:

b/lmdb/db_lmdb.cpp:77   Attempt to get uncle from height 416773 failed -- block
not in db
2019-05-25 02:16:20.326 [P2P6]  WARNING blockchain.db.lmdb      src/blockchain_d
b/lmdb/db_lmdb.cpp:3210 WARNING: batch transaction mode already enabled, but ask
ed to enable batch mode
2019-05-25 02:16:20.359 [P2P6]  INFO    global  src/cryptonote_core/blockchain.c
pp:1220 ←[1;32mREORGANIZE SUCCESS! on height: 416774, new blockchain size: 41677
6 top block <19ed42e474d38b6b60e2453134fcceb37192614a7b8a1fdd8c231802476d9c27> c
umulative difficulty 7228933903442 cumulative weight 7235755313095←[0m
2019-05-25 03:25:21.124 [P2P7]  INFO    global  src/cryptonote_protocol/cryptono
te_protocol_handler.inl:311     [103.107.102.234:22423 OUT] Sync data returned a
 new top block candidate: 416990 -> 416623 [Your node is 367 blocks (0 days) ahe
ad]
SYNCHRONIZATION started
2019-05-25 03:25:24.600 [P2P6]  INFO    global  src/cryptonote_protocol/cryptono
te_protocol_handler.inl:1614    ←[1;32mSYNCHRONIZED OK←[0m

in the fork goes and rebuilds the chain.
In a network of several chains?

[GD199]

how can u restore a wallet from a seed?

--restore-deterministic-wallet does not seem to work

[traaitt]

Hello,
I get this "error". Does anyone knows how to fix it?

2019-05-25 14:50:40.973 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [23.116.117.232:22423 OUT] Sync data returned a new top block candidate: 418634 -> 419019 [Your node is 385 blocks (0 days) behind]
SYNCHRONIZATION started

[Solo-Project]

Forr quick help please visit the discord.  We cannot reply to every technical support request in this thread:

http://discord.minesolo.com/

cratex daemon is in sync per the admin

[Solo-Project]

We are pleased to announce that another exchange partner (FirstCryptoBank) has listed Solo (XSL) with three trading pairs:

https://fcbaccount.com/fcb/exchange/BTC/XSL
https://fcbaccount.com/fcb/exchange/LTC/XSL
https://fcbaccount.com/fcb/exchange/DOGE/XSL

[lucky80]

We are pleased to announce that another exchange partner (FirstCryptoBank) has listed Solo (XSL) with three trading pairs:

https://fcbaccount.com/fcb/exchange/BTC/XSL
https://fcbaccount.com/fcb/exchange/LTC/XSL
https://fcbaccount.com/fcb/exchange/DOGE/XSL

The new exchange brings new community and new spirit. The southXchange voting is closing to the top three. I am sure we will reach the top.


Good job guys! I will take a peek at the new soul.

[casper77]

strange things
why my balance became less after update ?

You were possibly mining on a fork - one thing that you can try is this to rescan your wallet from block 0:

set refresh-from-block-height 0
rescan_bc

the same balance after that - lesser than before update
should we update before 30 may or nevermind ?

smaller balance then before update
no new blocks about 1 day on 5 kH
seems to i don't like your project

[cryptomaxsun]

strange things
why my balance became less after update ?

You were possibly mining on a fork - one thing that you can try is this to rescan your wallet from block 0:

set refresh-from-block-height 0
rescan_bc

the same balance after that - lesser than before update
should we update before 30 may or nevermind ?

smaller balance then before update
no new blocks about 1 day on 5 kH
seems to i don't like your project

I updated, blocks are regularly on 2 kh/s find, the daemon sometimes can not synchronize or goes to another chain.
Check, can you in another chain?
The height of the blocks with the explorer must match.
Explorer - http://explorer.minesolo.com/

[casper77]

set refresh-from-block-height 0
which value should set for getting actual balance but not wait refresh from zero ?

[casper77]

game over ?
no buy orders even for 1 satoshi
i shutting down my cores

[cryptomaxsun]

game over ?
no buy orders even for 1 satoshi
i shutting down my cores

Yes, even in the morning there were orders for 1 satoshi, and now it has been removed.
But recently there was a pump until 7 Satoshi.
And 2 satoshi instantly bought up.

And the difficulty of the network has decreased.
I continue mining, the developer is still here and continues to develop.

[watt2mine]

And the difficulty of the network has decreased.
I continue mining, the developer is still here and continues to develop.

I think that now it's worth mining even more, buyers come and go time after time.
I do confirm that network's hash rate is lower since I found more blocks per day too 

[Solo-Project]

We are pleased to announce that our third exchange partner (TradeCX) has listed Solo (XSL):

https://tradecx.io/markets/xslbtc

[casper77]

is cratex on right chain ? i can't make deposit, 6 hours already since transaction was made