🚀🌕[ANN] [RSL] [POW/Scrypt8K] [Low Premine] LiteNote: the solution to email spam

[Ronsor]

LiteNote
Communications for the 21st century

WE ARE SWITCHING OUR TICKER TO RSL TO PREVENT CONFLICT

• Ticker: RSL
• Max Supply: 9.6 billion RSL
• Block Time: 150 seconds
• Algorithm: Scrypt8K
• Premine: less than 1%
• Exchanges: <pending>

GUI Wallet and Message Client
Latest Version: 2.0.17.1c

• Windows: https://github.com/LiteNoteProject/litenote-tk/releases/download/2.0.17.1c/litenote-full-win64.zip
• Linux: https://github.com/LiteNoteProject/litenote-tk/releases/download/2.0.17.1c/litenote-full-linux64.tar.gz
• macOS Coming Soon!

About

The future of communications is now. Traditional email has problems ranging from reliability to just too much spam. LiteNote (RSL), a cryptocurrency with support for built in email-like messaging, solves all these problems.

Using our new model, spam can be stopped just by ignoring it. Sending a message costs a small amount of LiteNote, and you get LiteNote whenever you receive a message. If you do not reply to spammers, they will eventually run out of LiteNote and be unable to send more spam.

Website & More Downloads

yaddu (primary support community) - telegram

Earn LiteNote By Sharing It With Friends!

Buy LiteNote with Bitcoin

Whitepaper

[pochy123]

how can we mine?

[Ronsor]

how can we mine?

you can do it easiest using the GUI:

Mining -> Start Mining

Mining will continue while the GUI is open

[WhyMe]

XRN already exists, Saronite ...

[Ronsor]

XRN already exists, Saronite ...

I guess I'll change to RSL

[thin]

The future of communications is now. Traditional email has problems ranging from reliability to just too much spam. LiteNote (RSL), a cryptocurrency with support for built in email-like messaging, solves all these problems.

Using our new model, spam can be stopped just by ignoring it. Sending a message costs a small amount of LiteNote, and you get LiteNote whenever you receive a message. If you do not reply to spammers, they will eventually run out of LiteNote and be unable to send more spam.

E-mail is standard and free. Paid non standard service as you propose has no chances at all. Of course it could work in a  small closed community, but even there everyone could be free of spam by simply avoiding disclosing e-mail to outside of the group.

[yanoaziz]

virus detecter par mon chrome? anyway, I am out hacker is everywhere 

[Ronsor]

virus detecter par mon chrome? anyway, I am out hacker is everywhere 

It's not a virus. Chrome just doesn't like software it hasn't seen before.

[Zud71]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'
channel discord???

[Ronsor]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'

Mining should work in Litenote GUI.

For the CLI, create a .bat file: mining.bat

put inside:

Code:

:loop
litenote-cli --rpcuser=null --rpcpassword=null generate 1
goto :loop

run it

[Zud71]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'

Mining should work in Litenote GUI.

For the CLI, create a .bat file: mining.bat

put inside:

Code:

:loop
litenote-cli --rpcuser=null --rpcpassword=null generate 1
goto :loop

run it

I did, but the CPU load 0% - the generation does not go?

[jimboscott]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'

Mining should work in Litenote GUI.

For the CLI, create a .bat file: mining.bat

put inside:

Code:

:loop
litenote-cli --rpcuser=null --rpcpassword=null generate 1
goto :loop

run it

Not working.  CLI client does not default to proper RPC configuration and nowhere is that documented.

Also - this...

'2019-07-10T20:59:57Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2530
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2531
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2532
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2533
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2534
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2537
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2548
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2550
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2551
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2552
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2553
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2554
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2555
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2569
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2637
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2743
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2800
2019-07-10T21:00:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2917 etc etc etc.


'Make sure the litenoted server is running and that you are connecting to the correct RPC port.'

My server is running... but where do I configure the port?

[Ronsor]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'

Mining should work in Litenote GUI.

For the CLI, create a .bat file: mining.bat

put inside:

Code:

:loop
litenote-cli --rpcuser=null --rpcpassword=null generate 1
goto :loop

run it

Not working.  CLI client does not default to proper RPC configuration and nowhere is that documented.


Also - this...

'2019-07-10T20:59:57Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2530
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2531
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2532
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2533
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2534
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2537
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2548
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2550
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2551
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2552
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2553
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2554
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2555
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2569
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2637
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2743
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2800
2019-07-10T21:00:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2917 etc etc etc.


'Make sure the litenoted server is running and that you are connecting to the correct RPC port.'

My server is running... but where do I configure the port?

If litenoted isn't running with rpcuser/rpcpassword set to null/null, then remove `--rpcuser=null --rpcpassword=null` from the generate command.

[jimboscott]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'

Mining should work in Litenote GUI.

For the CLI, create a .bat file: mining.bat

put inside:

Code:

:loop
litenote-cli --rpcuser=null --rpcpassword=null generate 1
goto :loop

run it

The daemon is still just flooding with this...

2019-07-10T21:07:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12710
2019-07-10T21:07:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12722
2019-07-10T21:07:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12724
2019-07-10T21:07:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12725
2019-07-10T21:07:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12726
2019-07-10T21:07:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12727
2019-07-10T21:07:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12728
2019-07-10T21:07:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12738
2019-07-10T21:07:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12833
2019-07-10T21:07:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12935
2019-07-10T21:07:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13021
2019-07-10T21:07:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13135
2019-07-10T21:07:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13210
2019-07-10T21:07:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13303
2019-07-10T21:07:06Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13386
2019-07-10T21:07:06Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13471
2019-07-10T21:07:06Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13536
2019-07-10T21:07:07Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13537
2019-07-10T21:07:07Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13538
2019-07-10T21:07:08Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13539
2019-07-10T21:07:08Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13540
2019-07-10T21:07:09Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13541
2019-07-10T21:07:09Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13542
2019-07-10T21:07:09Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13543
2019-07-10T21:07:10Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13553
2019-07-10T21:07:10Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13554
2019-07-10T21:07:11Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13555
2019-07-10T21:07:11Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13556
2019-07-10T21:07:12Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13575
2019-07-10T21:07:12Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13576


Not working.  CLI client does not default to proper RPC configuration and nowhere is that documented.


Also - this...

'2019-07-10T20:59:57Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2530
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2531
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2532
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2533
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2534
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2537
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2548
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2550
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2551
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2552
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2553
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2554
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2555
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2569
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2637
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2743
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2800
2019-07-10T21:00:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2917 etc etc etc.


'Make sure the litenoted server is running and that you are connecting to the correct RPC port.'

My server is running... but where do I configure the port?

If litenoted isn't running with rpcuser/rpcpassword set to null/null, then remove `--rpcuser=null --rpcpassword=null` from the generate command.

Sorry - got caught in the wrong part of the thread.

The dameon is constantly spamming that there is an incorrect password attempt as seen above.

Also, the GUI wallet is nothing but a blank window on my machine. 

[Ronsor]

how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'

Mining should work in Litenote GUI.

For the CLI, create a .bat file: mining.bat

put inside:

Code:

:loop
litenote-cli --rpcuser=null --rpcpassword=null generate 1
goto :loop

run it

The daemon is still just flooding with this...

2019-07-10T21:07:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12710
2019-07-10T21:07:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12722
2019-07-10T21:07:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12724
2019-07-10T21:07:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12725
2019-07-10T21:07:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12726
2019-07-10T21:07:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12727
2019-07-10T21:07:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12728
2019-07-10T21:07:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12738
2019-07-10T21:07:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12833
2019-07-10T21:07:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:12935
2019-07-10T21:07:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13021
2019-07-10T21:07:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13135
2019-07-10T21:07:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13210
2019-07-10T21:07:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13303
2019-07-10T21:07:06Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13386
2019-07-10T21:07:06Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13471
2019-07-10T21:07:06Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13536
2019-07-10T21:07:07Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13537
2019-07-10T21:07:07Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13538
2019-07-10T21:07:08Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13539
2019-07-10T21:07:08Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13540
2019-07-10T21:07:09Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13541
2019-07-10T21:07:09Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13542
2019-07-10T21:07:09Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13543
2019-07-10T21:07:10Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13553
2019-07-10T21:07:10Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13554
2019-07-10T21:07:11Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13555
2019-07-10T21:07:11Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13556
2019-07-10T21:07:12Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13575
2019-07-10T21:07:12Z ThreadRPCServer incorrect password attempt from 127.0.0.1:13576


Not working.  CLI client does not default to proper RPC configuration and nowhere is that documented.


Also - this...

'2019-07-10T20:59:57Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2530
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2531
2019-07-10T20:59:58Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2532
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2533
2019-07-10T20:59:59Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2534
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2537
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2548
2019-07-10T21:00:00Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2550
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2551
2019-07-10T21:00:01Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2552
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2553
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2554
2019-07-10T21:00:02Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2555
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2569
2019-07-10T21:00:03Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2637
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2743
2019-07-10T21:00:04Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2800
2019-07-10T21:00:05Z ThreadRPCServer incorrect password attempt from 127.0.0.1:2917 etc etc etc.


'Make sure the litenoted server is running and that you are connecting to the correct RPC port.'

My server is running... but where do I configure the port?

If litenoted isn't running with rpcuser/rpcpassword set to null/null, then remove `--rpcuser=null --rpcpassword=null` from the generate command.

Sorry - got caught in the wrong part of the thread.

The dameon is constantly spamming that there is an incorrect password attempt as seen above.

Also, the GUI wallet is nothing but a blank window on my machine. 

If you started the daemon seperately, you have to kill it before you can use the GUI wallet.

The GUI wallet sets up the daemon with the correct parameters

[jimboscott]

OK - killed the daemon and ran the GUI wallet.  Got a couple of errors pop up but it seems to have gotten over those issues.  Will know in a bit if mining is working.

[dez82]

So, this is a new messaging platform that doesn't allow sending to email addresses, only addresses within the blockchain, but without the adoption of email.

Why not actually make a mailserver with a @litenote.net domain name that allows sending, then uses a neural net based on other spam detected on the blockchain to build a database of spam to work with?

All you've really done here is make a crappy knockoff of chatcoin but not in realtime. I can do the same thing by sending 1 DOGE and putting a comment against the transaction.

[Ronsor]

So, this is a new messaging platform that doesn't allow sending to email addresses, only addresses within the blockchain, but without the adoption of email.

Why not actually make a mailserver with a @litenote.net domain name that allows sending, then uses a neural net based on other spam detected on the blockchain to build a database of spam to work with?

All you've really done here is make a crappy knockoff of chatcoin but not in realtime. I can do the same thing by sending 1 DOGE and putting a comment against the transaction.

Comments are not stored in the blockchain actually.

Email gateway software is planned.

Messages are received instantly, even if the coins received along with them are not confirmed yet.

[pochy123]

it seems that clogs the chain

[Ronsor]

it seems that clogs the chain

what does?