Pages:
Author

Topic: [ANN] [XSL] Solo - A secure, private, censorship resistant cryptocurrency - page 5. (Read 4921 times)

jr. member
Activity: 41
Merit: 1
hero member
Activity: 1316
Merit: 514
Instead of mining i decided just to buy at 1 sat Cheesy Mining continuously using my CPU will toast and burn it in the long run so not worth the current price now. Let's start some market making and lets bring XSL to 10 sats Cheesy for setting up a support in 1 sat and waiting for dumpers.
legendary
Activity: 2884
Merit: 1035
can't start mining, sync is not completed, stay in 382798 block 2 hours...
what i should do?

do you synchronize from zero or from blockchain snapshot ?
hero member
Activity: 1652
Merit: 593
can't start mining, sync is not completed, stay in 382798 block 2 hours...
what i should do?


Please ask in discord for an effective solution, meanwhile, restart your daemon
newbie
Activity: 35
Merit: 0
can't start mining, sync is not completed, stay in 382798 block 2 hours...
what i should do?




2019-05-18 22:24:23.921 13516   INFO    global  src/daemon/main.cpp:214 Solo 'Han' (v1.0.4.4-9d37987)
2019-05-18 22:24:23.922 13516   INFO    global  src/daemon/protocol.h:53        Initializing cryptonote protocol...
2019-05-18 22:24:23.922 13516   INFO    global  src/daemon/protocol.h:58        Cryptonote protocol initialized OK
2019-05-18 22:24:23.923 13516   INFO    global  src/daemon/p2p.h:63     Initializing p2p server...
2019-05-18 22:24:27.944 13516   INFO    global  src/daemon/p2p.h:68     p2p server initialized OK
2019-05-18 22:24:27.946 13516   INFO    global  src/daemon/rpc.h:63     Initializing core RPC server...
2019-05-18 22:24:27.946 13516   INFO    global  contrib/epee/include/net/http_server_impl_base.h:77     Binding on 127.0.0.1:22424
2019-05-18 22:24:27.947 13516   INFO    global  src/daemon/rpc.h:69     core RPC server initialized OK on port: 22424
2019-05-18 22:24:27.947 13516   INFO    global  src/daemon/core.h:74    Initializing core...
2019-05-18 22:24:27.948 13516   INFO    global  src/cryptonote_core/cryptonote_core.cpp:416     Loading blockchain from folder C:\ProgramData\solo\lmdb ...
2019-05-18 22:24:27.976 13516   INFO    global  src/cryptonote_core/cryptonote_core.cpp:514     Loading checkpoints
2019-05-18 22:24:27.978 13516   INFO    global  src/daemon/core.h:79    Core initialized OK
2019-05-18 22:24:27.978 13516   INFO    global  src/daemon/rpc.h:74     Starting core RPC server...
2019-05-18 22:24:27.979 [SRV_MAIN]      INFO    global  src/daemon/rpc.h:79     core RPC server started ok
2019-05-18 22:24:27.999 [SRV_MAIN]      INFO    global  src/daemon/p2p.h:78     Starting p2p net loop...
2019-05-18 22:24:29.001 [P2P7]  INFO    global  src/cryptonote_core/cryptonote_core.cpp:1494
**********************************************************************
The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through "set_log " command,
where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).

Use the "help" command to see the list of available commands.
Use "help " to see a command's documentation.
**********************************************************************

2019-05-18 22:24:29.506 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [46.72.106.45:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390209 [Your node is 7411 blocks (1 days) behind]
SYNCHRONIZATION started
2019-05-18 22:24:33.847 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [221.219.179.84:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390209 [Your node is 7411 blocks (1 days) behind]
SYNCHRONIZATION started
2019-05-18 22:24:39.534 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [221.219.179.84:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390210 [Your node is 7412 blocks (1 days) behind]
SYNCHRONIZATION started
2019-05-18 22:24:42.264 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [221.219.179.84:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390210 [Your node is 7412 blocks (1 days) behind]
SYNCHRONIZATION started
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
Thank you!
Just started mining at 2 kh/s, immediately found a block.
It was just luck.
With difficulty 22.85 M, should be about 7 blocks per day.
newbie
Activity: 1
Merit: 0
I started the miner through the daemon.
But hashrate is not specified.
How can I find out the hashrate of my processor in to calculate the chances of finding a block?

type
Quote
status

type
Quote
show_hr
to know lifetime your hashrate

and type
Quote
hide_hr
to hide your hashrate
legendary
Activity: 2884
Merit: 1035
I started the miner through the daemon.
But hashrate is not specified.
How can I find out the hashrate of my processor in to calculate the chances of finding a block?

show_hr in daemon window
as for chances i have 8 blocks per day on 6 core CPU
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
I started the miner through the daemon.
But hashrate is not specified.
How can I find out the hashrate of my processor in to calculate the chances of finding a block?
newbie
Activity: 75
Merit: 0
symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP

i am getting this error since the last update
newbie
Activity: 75
Merit: 0
hero member
Activity: 1652
Merit: 593
as i understand should leave open window with synced daemon and start mining in solo-wallet-cli, right ?

nope. just open your daemon and mine through it. Please join our discord man
legendary
Activity: 2884
Merit: 1035
as i understand should leave open window with synced daemon and start mining in solo-wallet-cli, right ?
hero member
Activity: 1652
Merit: 593
0.28 BTC worth of buy order in 1 sats price Cheesy that guy must be dreaming. But its a good start, It dumps from 100 sats to 3 sats in a few hours after listing. Dumpers everywhere.
After Exchange listing what next for XSL?

Let them dump, At least we have price movement now. It was a small market test for XSL.
hero member
Activity: 1316
Merit: 514
We are pleased to announce our first exchange partner cratex.io has listed Solo (XSL) with three trading pairs.

XSL/BTC - https://cratex.io/index.php?pair=XSL/BTC
XSL/LTC - https://cratex.io/index.php?pair=XSL/LTC
XSL/BTCZ - https://cratex.io/index.php?pair=XSL/BTCZ

0.28 BTC worth of buy order in 1 sats price Cheesy that guy must be dreaming. But its a good start, It dumps from 100 sats to 3 sats in a few hours after listing. Dumpers everywhere.

After Exchange listing what next for XSL?

jr. member
Activity: 41
Merit: 1
We are pleased to announce our first exchange partner cratex.io has listed Solo (XSL) with three trading pairs.

XSL/BTC - https://cratex.io/index.php?pair=XSL/BTC
XSL/LTC - https://cratex.io/index.php?pair=XSL/LTC
XSL/BTCZ - https://cratex.io/index.php?pair=XSL/BTCZ
jr. member
Activity: 41
Merit: 1
Optional Update Today

v1.0.4.3
-Remove lingering CURL depends
-Revise seed nodes

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

Windows ( https://minesolo.com/release/solo-v1.0.4.3-win64.zip )
Windows NO AES ( https://minesolo.com/release/solo-v1.0.4.3-win64-NO_AES.zip )
Linux ( https://minesolo.com/release/solo-v1.0.4.3-linux64.tar.gz )
Source ( https://gitlab.com/solo-project/solo )
jr. member
Activity: 41
Merit: 1
Optional Update Today

v1.0.4.2
-code cleanup for obsolete functions
-remove dependency for obsolete functions

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

Windows ( https://minesolo.com/release/solo-v1.0.4.2-win64.zip )
Windows NO AES ( https://minesolo.com/release/solo-v1.0.4.2-win64-NO_AES.zip )
Linux ( https://minesolo.com/release/solo-v1.0.4.2-linux64.tar.gz )
Source ( https://gitlab.com/solo-project/solo )
jr. member
Activity: 41
Merit: 1
Optional but highly recommended upgrade today. This upgrade will improve your ability to stay in sync with the network and reduce banning of other nodes.

v1.0.4.1
-Ban logic improved to eliminate unintentional banning of peers
-Sync improvements

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

Important Note:
the bootstrap method used up to this version is no longer the recommended method to initially sync to the network and the blockchain.raw will no longer be published. In its place is a blockchain database snapshot. We recommend re-syncing your node to achieve maximum results one of the following two ways:

Slow:
Delete the lmdb directory (~/.solo on Linux) (C:\ProgramData\solo\ on Windows) restart solod and let it sync from 0. This was performed on multiple nodes and took several hours, most had to restart the daemon a couple times. Your mileage will vary depending on factors such as connection and hardware. We are still working to improve a full blockchain sync.

Fast:
Delete the existing database and import the snapshot.

Windows importing:
Download https://minesolo.com/release/snapshot.zip
Remove contents of C:\ProgramData\solo\ extract contents of snapshot.zip to the same directory.

Linux import:
cd ~ && rm -Rf ~/.solo && mkdir .solo && cd .solo && wget https://minesolo.com/release/snapshot.tar.gz && tar xfv snapshot.tar.gz

Note that if this is your first time to sync or you use a custom path you will not have these directories. Launching solod will create them or they can be created manually. Also, for Windows users C:\ProgramData\ is a hidden folder by default, it can be accessed by showing hidden folders or by typing C:\ProgramData\solo\ into the address line of file explorer or the run command (windows key + r).
jr. member
Activity: 41
Merit: 1
Mandatory upgrade today to v1.0.4.0 as we are now hard forking at block 350001 to v17.  Notable changes:

v1.0.4.0:
-Block any nodes earlier than v1.0.4.0
-DAA Window adjusted to 400 blocks from 180 in v17
-Revise Seed nodes
-Change CRYPTONOTE_DEFAULT_TX_SPENDABLE_AGE to 20 from 5
-Change all async params to 1000
-Changes to prepare_handle_incoming_blocks

Windows (https://minesolo.com/release/solo-v1.0.4.0-win64.zip)
Windows NO AES ( https://minesolo.com/release/solo-v1.0.4.0-win64-NO_AES.zip )
Linux ( https://minesolo.com/release/solo-v1.0.4.0-linux64.tar.gz )
Source ( https://gitlab.com/solo-project/solo )
Pages:
Jump to: