Topic: 🚀🌕[ANN] [RSL] [POW/Scrypt8K] [Low Premine] LiteNote: the solution to email spam (Read 1047 times)
March 12, 2020, 04:56:36 AM
КAК УЗHATЬ БAЛAHC MOHET И КAК OTПPABИTЬ
August 08, 2019, 04:43:40 PM
exchanges?
July 16, 2019, 03:53:07 PM
IMPORTANT WARNING: someone has been trying to spread malware disguised as a "litenote-qt" wallet. THERE IS NO SUCH THING. If you have run this malware, please reinstall Windows.
July 15, 2019, 12:43:03 PM
downloaded and deleted, this remind me his old project: Rcoin, which said it's a new coin with no blockchain
but it's totally fake!
but it's totally fake!
how is it fake?
edit: I specifically deny any accusations of this project being fake. You can read the source if you still think it's fake.
July 15, 2019, 11:47:58 AM
downloaded and deleted, this remind me his old project: Rcoin, which said it's a new coin with no blockchain
but it's totally fake!
but it's totally fake!
July 13, 2019, 02:44:18 PM
only orphan blocks
July 13, 2019, 09:03:49 AM
hi Dev what is RPC Port? not port thanks..
July 12, 2019, 07:40:27 PM
it seems someone mining with gpu?
hard to mine now
hard to mine now
July 12, 2019, 10:32:59 AM
We've upgraded to 2.0.17.1c which fixes a minor bug in the GUI (litenote-tk issue #1)
July 11, 2019, 10:52:02 AM
it seems that clogs the chain
what does?2019-07-11T01:17:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 733 seconds ago)
2019-07-11T01:20:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 913 seconds ago)
2019-07-11T01:21:37Z UpdateTip: new best=74e594a6658d9184eb846d5fa71ed677173ea6d7bb637084f33d84a5af87d0f0 height=2896 version=0x20000000 log2_work=23.975288 tx=2917 date='2019-07-11T01:16:58Z' progress=1.000000 cache=0.2MiB(1103txo)
2019-07-11T01:29:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 469 seconds ago)
2019-07-11T01:32:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 649 seconds ago)
2019-07-11T01:32:29Z UpdateTip: new best=92b237240d0c13dd709e0285eb6fa650e665f6570b5646a2e17ad6e090361764 height=2897 version=0x20000000 log2_work=24.026898 tx=2918 date='2019-07-11T01:22:02Z' progress=1.000000 cache=0.2MiB(1104txo)
2019-07-11T01:35:04Z New outbound peer connected: version: 70015, blocks=35, peer=2
2019-07-11T01:35:54Z CreateNewBlock(): block weight: 908 txs: 0 fees: 0 sigops 400
2019-07-11T01:41:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 537 seconds ago)
2019-07-11T01:44:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 717 seconds ago)
2019-07-11T01:46:09Z [default wallet] keypool added 1 keys (0 internal), size=2000 (1000 internal)
2019-07-11T01:46:09Z [default wallet] keypool reserve 44
2019-07-11T01:46:09Z CreateNewBlock(): block weight: 908 txs: 0 fees: 0 sigops 400
2019-07-11T01:47:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 897 seconds ago)
Oh no... network difficulty has just increased so it takes like 15 minutes to get a block. Should be ok in a week or two.
An important update has been released that fixes this issue at block 2890.
July 10, 2019, 09:00:57 PM
it seems that clogs the chain
what does?2019-07-11T01:17:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 733 seconds ago)
2019-07-11T01:20:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 913 seconds ago)
2019-07-11T01:21:37Z UpdateTip: new best=74e594a6658d9184eb846d5fa71ed677173ea6d7bb637084f33d84a5af87d0f0 height=2896 version=0x20000000 log2_work=23.975288 tx=2917 date='2019-07-11T01:16:58Z' progress=1.000000 cache=0.2MiB(1103txo)
2019-07-11T01:29:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 469 seconds ago)
2019-07-11T01:32:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 649 seconds ago)
2019-07-11T01:32:29Z UpdateTip: new best=92b237240d0c13dd709e0285eb6fa650e665f6570b5646a2e17ad6e090361764 height=2897 version=0x20000000 log2_work=24.026898 tx=2918 date='2019-07-11T01:22:02Z' progress=1.000000 cache=0.2MiB(1104txo)
2019-07-11T01:35:04Z New outbound peer connected: version: 70015, blocks=35, peer=2
2019-07-11T01:35:54Z CreateNewBlock(): block weight: 908 txs: 0 fees: 0 sigops 400
2019-07-11T01:41:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 537 seconds ago)
2019-07-11T01:44:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 717 seconds ago)
2019-07-11T01:46:09Z [default wallet] keypool added 1 keys (0 internal), size=2000 (1000 internal)
2019-07-11T01:46:09Z [default wallet] keypool reserve 44
2019-07-11T01:46:09Z CreateNewBlock(): block weight: 908 txs: 0 fees: 0 sigops 400
2019-07-11T01:47:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 897 seconds ago)
Oh no... network difficulty has just increased so it takes like 15 minutes to get a block. Should be ok in a week or two.
July 10, 2019, 08:51:00 PM
it seems that clogs the chain
what does?2019-07-11T01:17:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 733 seconds ago)
2019-07-11T01:20:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 913 seconds ago)
2019-07-11T01:21:37Z UpdateTip: new best=74e594a6658d9184eb846d5fa71ed677173ea6d7bb637084f33d84a5af87d0f0 height=2896 version=0x20000000 log2_work=23.975288 tx=2917 date='2019-07-11T01:16:58Z' progress=1.000000 cache=0.2MiB(1103txo)
2019-07-11T01:29:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 469 seconds ago)
2019-07-11T01:32:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 649 seconds ago)
2019-07-11T01:32:29Z UpdateTip: new best=92b237240d0c13dd709e0285eb6fa650e665f6570b5646a2e17ad6e090361764 height=2897 version=0x20000000 log2_work=24.026898 tx=2918 date='2019-07-11T01:22:02Z' progress=1.000000 cache=0.2MiB(1104txo)
2019-07-11T01:35:04Z New outbound peer connected: version: 70015, blocks=35, peer=2
2019-07-11T01:35:54Z CreateNewBlock(): block weight: 908 txs: 0 fees: 0 sigops 400
2019-07-11T01:41:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 537 seconds ago)
2019-07-11T01:44:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 717 seconds ago)
2019-07-11T01:46:09Z [default wallet] keypool added 1 keys (0 internal), size=2000 (1000 internal)
2019-07-11T01:46:09Z [default wallet] keypool reserve 44
2019-07-11T01:46:09Z CreateNewBlock(): block weight: 908 txs: 0 fees: 0 sigops 400
2019-07-11T01:47:26Z Potential stale tip detected, will try using extra outbound peer (last tip update: 897 seconds ago)
July 10, 2019, 08:19:47 PM
por favor agregue pool
July 10, 2019, 07:49:46 PM
July 10, 2019, 06:52:04 PM
it seems that clogs the chain
July 10, 2019, 05:27:19 PM
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.
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.
July 10, 2019, 04:35:19 PM
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.
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.
July 10, 2019, 04:26:01 PM
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.
July 10, 2019, 04:16:25 PM
how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'
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
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
July 10, 2019, 04:07:49 PM
how to start mining through litenote-cli.exe in windows?
litenote-gui.exe - does not work. Error Windows cannot find '--rpcpassword=null'
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
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.
Jump to: