|
Morning update.
I have posted about using good power adapter for running your RPi
The cheap ones can run the range from total crap to good.
One of our customers used to have a business selling cheap cell phone accessories, when he stopped doing that we (the people I work for) wound up with a lot of his old stock. The running joke is if you need a phone charger take 2 because one of them probably will not work. Yeah, that bad.
So yesterday I took 4 to run a test.
4 of the exact same setup. RPi3 + high endurance SD card + Toshiba 500GB external usb drive + one of these cheap ass power adapters.
I installed RaspiBlitz on all of them, got them started on the updates and went to bed.
This was the BEST of them: UndervoltageReports in Logs: 4
This is the worst of them: [Left blank because it failed]
If you are doing this spend more then the cost of a cup of coffee on your power supply people.
-Dave
*I am doing this testing for things other then running a bitcoin node but whatever you are doing with it the point remains the same.
|
|
|
|
If you are talking about the original bitcoin then all you need is the wallet.dat file. There is no seed phrase in the original software. Take a look here for more info: https://bitcointalk.org/index.php?topic=4959742.0Oh, and DO A BACKUP OF THE FILE BEFORE DOING ANYTHING. -Dave |
|
|
|
It probably literally is your private keys or at least a way of transferring them across (potentially a master private).
I didn't realise your post here and was going to ask another question, do you have an option to close the channel I opened with you from your end? Like is it a verbose option or would it just be available via some reverse engineering.
I can do lncli closechannel e7568dc5d5f9c540f8f0c014f920da471d6648d8b4abc3447e241e73f9fdc524 0 and that should take care of it. I see your node as inactive are you having an issue? I will close it if you want, but if you are not going to be offline for long it would be better if your node sees the close. -Dave |
|
|
|
|
This is a bit of a lesson and a bit of just plain security.
There are utilities for for zap wallet / lnd and zeus / lnd to generate a QR code on the machine hosting your node to connect your mobile wallet to it.
These QR codes are the "keys to the kingdom" so to speak, think of them as private keys to a wallet. With them you can spend / open / close channels.
It's easy to forget this and keep a copy of the QR code someplace that might not be safe.
Don't do it.
-Dave
|
|
|
|
You did not say where you are or who your provider is but: Is your modem / router whatever provided by you or your ISP? If not what is the make / model? Same with your router / firewall. Yours or theirs? If yours make / model? If they supplied it it's their problem if you did that is usually the device they see. Moving into your network have you added anything? Wi-Fi speakers that were a Christmas gift? Other things? Smart bulb controller? PDF talking about it (long read) https://tinyurl.com/sqsczcz-Dave |
|
|
|
It's kind of funny, we all have our "lets nuke this user" person on the board. This must be our lucky day - cryptohunter is leaving, korner is leaving, CSW has finally proven to be the real Satoshi (one or all of those may not be true).
All of those are just background noise to me, spewing their crap, posting their junk and just being trolls. Game-protect now that is my user that I want gone. Yes, just another irrelevant troll, but I could really get behind a perma-ban on them. -Dave |
|
|
|
|
No matter how you want to talk to another machine on the internet you need to know it's IP.
At some point along the way you are going to need to know what it is.
If you are running a Windows / linux / whatever machine today unless you want to install another piece of software on top of it that connects in some new and different manner we are going to be stuck with DNS.
This has come up several times in several places on other sites I am on that have nothing to do with BTC. Always comes back to the same place DNS works so we keep it.
-Dave
|
|
|
|
No, pending open is different then pending closed. It shows up differently. These are just sitting out there in pending open. The joy of beta software  I was just looking for a way to make them go away for appearance sake when looking at it. -Dave |
|
|
|
|
Not sure if it is 2 weeks yet on one of them. If not it's close to two weeks on one of them.
I had this issue before on my old node and it was definitely over 2 weeks. Closer to 2 months that they were sitting out there pending.
I really don't want to take it to github, lots of reasons but mostly due to time, and the way people who are "there to help" can get snippy with you when you don't reply in a timely manner because, I don't know you might have to work and sleep now and then.
-Dave
|
|
|
|
Down over 11% and below $295. Wonder if there are enough BSV fans to prop it up. The actual release of the new client, already has stupidity involved: https://github.com/bitcoin-sv/bitcoin-sv/issues/125Oops, lets publish code that you can't verify the sig on. The other issue is (sort of) since it does have such a low market cap, [like every alt except perhaps ETH] it is somewhat easy to manipulate for someone with deep enough pockets. But they don't have to be super deep if you want to make a profit as the tide rises. -Dave |
|
|
|
Running lncli pendingchannels I get the following.
"total_limbo_balance": "0",
"pending_open_channels": [
{
"channel": {
"remote_node_pub": "02c00024c38031616f17f60dab1231477b52764e9f981fbecebe57ea518dc8610f",
"channel_point": "932418f98fe63e1f1e2433417f8770b6ae0114f0992adfa2384bfa8bd8868d16:0",
"capacity": "200000",
"local_balance": "0",
"remote_balance": "190950",
"local_chan_reserve_sat": "2000",
"remote_chan_reserve_sat": "2000"
},
"confirmation_height": 0,
"commit_fee": "9050",
"commit_weight": "552",
"fee_per_kw": "12500"
},
{
"channel": {
"remote_node_pub": "0340e22eb2c4c4e1793ee2e7100a695a4ed0899723484efcd00f48b5ccecb6b93f",
"channel_point": "53c3a1e790892da5967a757faa84a4635d9daf7678df5fe7d03a933730bd66e8:0",
"capacity": "110000",
"local_balance": "0",
"remote_balance": "109455",
"local_chan_reserve_sat": "1100",
"remote_chan_reserve_sat": "1100"
},
"confirmation_height": 0,
"commit_fee": "545",
"commit_weight": "552",
"fee_per_kw": "754"
Sometimes there is a 3rd that pops up and goes away. But, those are just sitting there. Nothing I do can remove them. It's just when I run that command or look in the RTL web interface I then have to go and check if they disappeared and someone else is opening a channel or it's just them. Last night was a good example, I had the 2 of them the odd 3rd one that comes and goes and yours. -Dave |
|
|
|
|
If the transaction was SENT but not CONFIRMED you may not see the address that the coins were sent to.
With mycelium (and most other wallets) *every* transaction gets a new address
So, if the funds were sent then it will show the next recieving address in line. BUT, if the transaction has not confirmed you might not see that address. Because once you hit reload it knows that address was used but since it was not confirmed it will not show an amount.
Yes, it's confusing but it's the way that mycelium shows stuff with a reload account.
-Dave
*Once it's confirmed you might actually have to reload again.
|
|
|
|
Gonna put a tokened response here to show I replied.
I'm opening up a channel with you and it should have 0.004 in capacity. I sent a low fee because its 4am here and I need sleep 😂. Sk it should confirm by the time I wake up.
Your channel opened. Still need help on removing the "phantom" channels. As I said for now it's no big deal but I can see it over time becoming an issue. -Dave |
|
|
|
Are you just trying to open a channel?
What address is funding it, can you look at it on a blockchain explorer?
I could try opening one with you but all I have is éclair?
Actually, if you could try to open one to me with eclair that would be an good test too. Is it something with Timelord2067 trying to connect to my node or is it something with eclair trying to connect to my node. I am about to go to sleep, it's been a busy couple of days, so I will check back in the morning here (GMT -5) -Dave |
|
|
|
you can "ban" the nodes you don't want to connect to. that is basically the manual version of what bitcoin core automatically does for bad nodes. the command name that you should use is setban and the details of how to use it is as follows: setban "subnet" "command" ( bantime absolute )
Attempts to add or remove an IP/Subnet from the banned list.
Arguments:
1. subnet (string, required) The IP/Subnet (see getpeerinfo for nodes IP) with an optional netmask (default is /32 = single IP)
2. command (string, required) 'add' to add an IP/Subnet to the list, 'remove' to remove an IP/Subnet from the list
3. bantime (numeric, optional, default=0) time in seconds how long (or until when if [absolute] is set) the IP is banned (0 or empty means using the default time of 24h which can also be overwritten by the -bantime startup argument)
4. absolute (boolean, optional, default=false) If set, the bantime must be an absolute timestamp in seconds since epoch (Jan 1 1970 GMT)
Examples:
> bitcoin-cli setban "192.168.0.6" "add" 86400
> bitcoin-cli setban "192.168.0.0/24" "add"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "setban", "params": ["192.168.0.6", "add", 86400] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
ref: https://bitcoincore.org/en/doc/0.19.0/rpc/network/setban/So, this was working fine. Then a small oops. Came in this AM to see how some things were syncing and instead of using the private IP they had looped in an out through the router. Just had to ban the public IP. Thanks, Dave |
|
|
|
Having the signature doesn't really affect my posting habits... what really affects my posting habits is my work roster!  Some weeks, I'll make like 10 posts because I'm busy working and/or too tired to look at the forum. Other weeks, I'm on standby or rostered days off and I hang out on the forum more... hell some weeks I'll end up way over the "max" number of paid posts. It's not like I say to myself "I must make X number of posts per week" to maximise revenue. I just participate as/when I feel I can... some weeks that is a lot and some weeks not so much. Heh, I can really relate to that today. I was expecting to be sitting on my ass surfing the web with not much to do. I made 1 post about 3 hours ago when I started work. Made a cup of coffee and now it's 3 hours later, my coffee is cold and I have not done anything online anywhere because the phone did not stop ringing. -Dave |
|
|
|
The key was imported, if you look at the output that flyx posted: user1@debian:~/gitian-builder$ gpg --keyserver keyserver.ubuntu.com --recv 40976EAF437D05B5
gpg: key 40976EAF437D05B5: 60 signatures not checked due to missing keys
gpg: key 40976EAF437D05B5: public key "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1 Unless debian does something different then most other linux systems it's there. Which was why I have no idea. -Dave |
|
|
|
|
.011
And stop playing around with corn, where are the clubs???
-Dave
|
|
|
|
|
Show Posts
