|
Zap seems the best looking one and pretty easy, unless i didnt miss something: "All Zap releases will be testnet only until further notice"
I am currently running a node on main net, seems like i should start a second on test as i am missing all the fun. most people are still pretty careful.
|
|
|
|
|
I am trying to find more resources and will put them in the OP. Also looking into getting some stats and figures on the nodes usage. Looking forward to see more topics around LN from the tech side.
|
|
|
|
I think I stumbled across guide about how to set up a BTC full node with lightning last week. Since I always wanted to run a full node on a pi, I took the chance to get both things done. I had a quick look at the search but it seems the topic isn't that big at the moment. However, I am very interested in that topic and want to look into the topic deeper the next week. Not sure if we have a good collection already but I would like to post the guides and stuff I find and maybe have some talks about it. I finished my node around 5h ago and so far it's running. I posted the guide I used down below. If i missed we have a good topic like this let me know, if not let's start one. Beginner’s Guide to ️⚡Lightning️⚡ on a Raspberry Pi - by Stadicus3000 |
|
|
|
|
I am glad to see the forum is at the same shit level as it has always been. No matter what people try to make it better, the sheer amount of bullshit happening here kills the effort. Good to see at least some folks keep fighting.
|
|
|
|
Yeah you are correct, it should ofc bind to both. I just took a break and checked again and then i noticed rpc isnt binding it self. At least someone confirms the issue thanks  this issue drives me crazy You are not alone. This is a bug in libevent, but it seems the debian package on raspberry pi doesn't have the fix. Other people already reported it: * https://github.com/litecoin-project/litecoin/issues/351 * https://bitcointalk.org/index.php?topic=2345585.0 (that crontab fix is ... well ... kinda shitty). * .. and a lot of other links I already closed. Try this, in /etc/systemd/system/bitcoind.service: [Unit]
Description=Bitcoin daemon
After=multi-user.target
Instead of " After=network.target", use " After=multi-user.target". It will start the service after the boot sequence. Not sure it will work on your raspberry pi, but it worked on mine: root@r01:/home/mycroft# netstat -nap|grep bitcoind|grep LISTEN
tcp 0 0 127.0.0.1:29000 0.0.0.0:* LISTEN 706/bitcoind
tcp 0 0 127.0.0.1:18332 0.0.0.0:* LISTEN 706/bitcoind
tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN 706/bitcoind
tcp6 0 0 ::1:18332 :::* LISTEN 706/bitcoind
tcp6 0 0 :::18333 :::* LISTEN 706/bitcoind
AWESOME! That did it! Thanks for helping me out |
|
|
|
After boot: tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN -
tcp6 0 0 ::1:18332 :::* LISTEN -
tcp6 0 0 :::18333 :::* LISTEN -
After kill: tcp 0 0 127.0.0.1:18332 0.0.0.0:* LISTEN -
tcp6 0 0 ::1:18332 :::* LISTEN -
Ahhhhh, what i now see is there is a binding on 18333 after boot (i am on testnet) and after my kill it switches to 18332. I'm reproducing the exact same problem on a raspberry pi. Interesting. I'll take a deeper look at it. root@r01:/home/mycroft# netstat -nap|grep bitcoin|grep LISTEN
tcp 0 0 127.0.0.1:29000 0.0.0.0:* LISTEN 573/bitcoind
tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN 573/bitcoind
tcp6 0 0 ::1:18332 :::* LISTEN 573/bitcoind
tcp6 0 0 :::18333 :::* LISTEN 573/bitcoind
root@r01:/home/mycroft#
Relevant debug lines: 2018-03-22 18:02:25 libevent: getaddrinfo: address family for nodename not supported
2018-03-22 18:02:25 Binding RPC on address 127.0.0.1 port 18332 failed.
EDIT: Okay, i dont see why but somehow btcd is binding it self to 18333 for some reason. ill check my configs again
It should listen both 18332 & 18333 ports on both ipv4 & ipv6. I think this is not a configuration problem, but a bug somewhere. Yeah you are correct, it should ofc bind to both. I just took a break and checked again and then i noticed rpc isnt binding it self. At least someone confirms the issue thanks this issue drives me crazy |
|
|
|
After boot: tcp 0 0 127.0.0.1:29000 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:10009 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 ::1:18332 :::* LISTEN -
tcp6 0 0 :::18333 :::* LISTEN -
After kill: tcp 0 0 127.0.0.1:29000 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:10009 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:18332 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 ::1:18332 :::* LISTEN -
Ahhhhh, what i now see is there is a binding on 18333 after boot (i am on testnet) and after my kill it switches to 18332. EDIT: Okay, i dont see why but somehow btcd is binding it self to 18333 for some reason. ill check my configs again |
|
|
|
bitcoin-cli is not able to reach the bitcoind's rpc port, which should be located at port 8332. You should try the following to check the port is correctly opened: # netstat -nap|grep bitcoin|grep LISTEN
tcp 0 0 127.0.0.1:8332 0.0.0.0:* LISTEN 13199/bitcoind
tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 13199/bitcoind
tcp6 0 0 ::1:8332 :::* LISTEN 13199/bitcoind
tcp6 0 0 :::8333 :::* LISTEN 13199/bitcoind
Also, make sure that bitcoind is started with the "-server" flag: # ps auxw|grep -i bitcoind|grep -v grep
coins 13199 8.2 3.7 1966860 619076 ? Ssl Mar10 1459:29 /home/coins/bin/bitcoin/bin/bitcoind -server -daemon
Thats all correct. As i said, if i kill the daemon and let systemd start it up again it works as it should. Config is set accodring to https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_30_bitcoin.mdEverything is working except when its starting during system boot. |
|
|
|
Not 100% if this is the right section but lets see. I am running the latest BTC daemon on a Raspberry Pi 3 with Stretch Lite and i followed this guide: https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_30_bitcoin.mdBasically, everything works except for one strange thing: If i reboot the system, bitcoind starts up on boot, runs and is "doing" something but if i want to use bitcoin-cli i get: bitcoin@pinode:/home/admin $ bitcoin-cli getblockchaininfo
error: couldn't connect to server: unknown (code -1)
(make sure server is running and you are connecting to the correct RPC port)
If i kill the btc daemon and wait till it gets upstarted by systemd again, everything is fine and working. i am sure the service config is good. Otherwise it shouldnt work with my hard kill. I changed my conf to: After=network-online.target Wants=network-online.target Cause i assumed the network stack is not ready but still the same. I have no clue why its not working from boot, well lets say why its only working half. Any suggestions? |
|
|
|
I would like to know if anyone is willing to trust those who have been involved in extortion attempts.
TMAN -- can you add this to the OP please?
Slowscammer, your bullshit accusations against me are still up and you failed to correct your claims. I would like to know why you are a such a retard. I would also like to know if you still do fake escrow scams and if you have banned lately. Oh wait, this was not about throwing stones? My bad... OP: * Possess/Manufacture/Sell Dangerous Weapon -> Your local gov does the same on a daily base. They earn while they kill. Whats the exact moral issue of this special case? |
|
|
|
cryptopia account nlexch account 10 uis sent me to check if it is scam. but it did not come for 10 hours so this site is a stock market in scam. and although the name on the uis official site is scam. please do not send your coins to this stock exchange for your security. your comment is scam. file a proper scam accusation or get lost |
|
|
|
NOW LIVE BITCHEZ!!! GET INSTA RICH!!! NO TIME TO EXPLAIN!!! It's a new type of agressive crypto markenting? Nice try, team Yeah, they will get all my money, at least what is left during the current lows... |
|
|
|
virustotal url checked show malicious, not me ! false positive |
|
|
|
|
7 pages of bullshit... I didn't do the math, but just assuming the average MN coin has a 120 seconds block time and at least 400 MNs online your deposit needs to be blocked at least 24h to get an average mn payment of one payout. unless you didn't hire someone from a 7th world country do all the work or scripted that 200%, that doesn't make any sense. 7 pages of newbie accs agreeing to each other with NO PROOF at all other than one screenshot is blatant.
So if someone who did put up those wild claims explains it in a way that actually makes sense BY MATH on a specific coin, we can talk about it. The posted screenshot proves nothing.
not saying SE is cool, just saying what has been posted doesn't make any sense to me. and btw: just because newbies agree with each other with no facts doesn't make it look legit. Put up some real prove that other people can verify. Saying "verified" means nothing....
|
|
|
|
so this gonna be relaunch again? wheres wallet anyway? you promise since since last month old thread https://bitcointalk.org/index.php?topic=2684868.0edit now i get it, dev was has a little problem with pirl team and he obviously not launch wallet its just for him to get premine lol it seems you didn't do you your research correct. |
|
|
|
I probably won't make changes in the near future, but I've been thinking about the captcha issue, and I wonder what people think about reCaptcha.
Where reCaptcha is used now, something is required, and AFAIK all other captcha services can be OCRed and are therefore useless. End-users often like SolveMedia, but those seem really easy to OCR. I actually really like the image classification approach on a theoretical level, though I hate relying on NSA-lite Google, and occasionally on Tor they throw you into some insane black hole of difficulty (though you can change your Tor exit to fix that).
how can someone complain about the NSA running Google and Cloudflare but still advertise TOR? Seems you have no issues with it, even its known where most of its funding is coming from... just curious... |
|
|
|
If your wallet is not syncing, please check if you have banned peers. Here is a list of working addnodes: addnode=171.6.145.211
addnode=86.125.115.165
addnode=92.51.61.81
addnode=95.8.48.221
addnode=176.51.254.219
addnode=77.37.236.232
addnode=73.189.43.93
addnode=35.176.72.145
addnode=171.6.195.74
addnode=62.216.205.186
addnode=212.164.230.172
addnode=125.70.163.100
addnode=176.114.6.7
addnode=172.222.188.172
addnode=90.188.31.182
addnode=88.254.210.141
addnode=212.87.179.34
addnode=85.104.102.164
addnode=113.53.134.80
addnode=91.66.85.212
addnode=92.243.166.76
addnode=109.187.117.223
addnode=36.81.73.69
addnode=83.217.206.155
addnode=46.242.87.218
addnode=213.87.153.76
addnode=217.144.172.5
addnode=71.63.215.84
addnode=1.179.247.254
addnode=45.63.104.114
addnode=184.82.233.233
addnode=185.92.222.163
addnode=192.227.174.12
addnode=104.162.107.191
addnode=46.4.88.116
addnode=58.8.152.102
addnode=94.25.160.78
addnode=202.44.36.107
addnode=84.17.23.45
addnode=93.37.83.205
addnode=73.10.255.44
addnode=213.136.84.127
addnode=71.68.16.230
addnode=94.214.192.89
addnode=183.88.56.121
addnode=184.22.218.75
addnode=188.163.70.191
addnode=81.206.211.44
addnode=94.28.152.7
addnode=90.155.165.98
addnode=176.12.32.153
addnode=91.239.69.6
addnode=47.74.145.69
addnode=95.27.42.3
addnode=89.106.198.71
addnode=94.19.104.91
addnode=5.254.241.66
addnode=95.25.114.90
addnode=146.66.182.66
addnode=2.123.64.243
addnode=178.72.70.108
addnode=54.36.252.117
addnode=124.120.236.204
addnode=52.166.110.242
addnode=178.164.254.235
addnode=1.0.201.224
addnode=58.8.152.188
addnode=77.28.12.192
addnode=91.201.230.251
addnode=5.128.179.72
addnode=112.215.238.191
addnode=37.59.48.93
addnode=31.173.84.108
addnode=185.212.171.216
addnode=112.215.239.191
addnode=14.232.239.102
addnode=88.207.219.133
addnode=80.209.224.189
addnode=193.69.62.94
addnode=46.61.152.191
addnode=77.95.56.221
addnode=27.224.106.54
addnode=39.67.0.47
addnode=36.79.164.117
addnode=62.216.205.96
addnode=49.48.247.156
addnode=122.190.94.24
addnode=73.30.182.144
addnode=223.206.111.87
addnode=130.255.58.37
addnode=119.76.120.121
addnode=2.92.209.51
addnode=49.144.130.5
addnode=46.219.234.245
addnode=201.75.10.109
addnode=36.5.90.120
addnode=118.172.93.226
addnode=184.22.160.236
|
|
|
|
UPDATED TO THE LATEST VERSION!  Come join the fun and get your mine on over at https://yiimp.masterhash.us/Stratum : stratum+tcp://yiimp.masterhash.us:4233
User : YOUR_GOA_ADDRESS
Password : c=GOA
Difficulty: d=
Website : https://yiimp.masterhash.us/
Payout : Every 1 hours
Fee : 0.5%
Example command line :
-a neoscrypt -o stratum+tcp://yiimp.masterhash.us:4233 -u YOUR_GOA_ADDRESS -p c=GOA |
|
|
|
Come join the fun and get your mine on over at https://yiimp.masterhash.us/Stratum : stratum+tcp://yiimp.masterhash.us:3833
User : YOUR_ECT_ADDRESS
Password : c=ECT
Difficulty: d=
Website : https://yiimp.masterhash.us/
Payout : Every 1 hours
Fee : 0.5%
Example command line :
-a nist5 -o stratum+tcp://yiimp.masterhash.us:3833 -u YOUR_ECT_ADDRESS -p c=ECT |
|
|
|
|
Show Posts
