Wouldn’t it be more beneficial to reward them based on efficiency as it relates to computational power / energy consumption? Again, it does. Efficiency is the work:energy ratio. A person who spends less energy than another, but generate the same number of hashes every second, gains a greater reward. [...] Sorry, but I lost you on the superblock header part. Can you describe how would this implementation make the system more efficient? Even if you changed some of the rules, as you say. Your phrasing is a little foggy.
|
|
|
There's no need to change anything in the source code. Currently they are rewarded based on the efficiency of their mining rigs. The more efficient a machine is, the more hashes it can calculate at the given cost, therefore, the more money they earn.
|
|
|
People store their coins on exchanges and other third party services all the time, which is exactly the same thing. It's not the same thing. I know few people who use Binance to trade shitcoins and few other who wanted to buy stuff with Bitcoin and used a similar exchange, but none who wants to keep their crypto in a vault they'll have no control upon, imagining they'll be safe there. That's hilariously tragic.
|
|
|
Bump. I've raised it to 3,000,000 sats as maximum.
|
|
|
Take a look on North Korea and their internet. It is limited, it is controlled (lol). Their internet is highly censored. The pages you can visit are limited, let alone the services that accept Bitcoin. There is no reason for a totalitarian government, of that level, to get involved; they already control everything. Even if I had high chances of getting away with it, I wouldn't even try, because there's a small chance I won't have a head afterwards.
|
|
|
For example IIRC Binance charges 10 USDT if you choose bitcoin chain and charges something like 0.1 if you use BinanceChain (since it is centralized they also don't need that many confirmation so the transfer is very fast too). Not only for centralization, if you allow me. It's clearly for their benefits. They want you to stop using BTC/ALTs as this would push you onto their shit-chain. Therefore, the shit-chain's demand increases. Also, I'm not quite sure, but they either charge large amounts so it can be confirmed instantly or you pay both Binance and the miners each time you make a transaction.
|
|
|
the title.. What will happen to the Bitcoin network if Russia blocks access to the internet? kinda gives away the scenario No internet doesn't necessarily mean they'll restrict the internet usage. I understood that they would simply limit it to their country only. I really think that the Russian government doesn't care about Bitcoin and it would ignore Bitcoin for sure. That isn't true. The minister of finance is pushing forward the regulation of cryptocurrencies, in general. In fact, I think we're in a period when every government is going to introduce them in their economic mechanism sooner or later. EU has withdrawn every one of their bad intentions regarding PoW. Biden took a step towards on regulating cryptocurrencies recently.
|
|
|
And I responded that 3 different block explorer would have 3x8 connections for a total of 24. How can you be sure about that? You have to trust the block explorers while the technology promotes the opposite. By running your own node, you trust no one. Don't you like the maximum number of connections? Increase it, it's in the source code. Be your own block explorer. The OP lost $80 on excess mobile data just from attempting sync Because they're doing it wrong. No one should use their mobile data to sync the chain, for the same reason they shouldn't use them to download a 4k 3-hour movie from a pirate site; better just buy it, it'll come cheaper!
|
|
|
Ooh. No internet. Got it now... Excuse me, I thought we're talking about a scenario where the country is simply incapable of connecting outside. It's hard to imagine a world without internet. ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
You do not have the ability to withdraw your coins without Coinbase's approval and cooperation. This is unbelievable. Are there people who use it, for real? Can't they realize there's something really faulty with it?
|
|
|
having no internet means no fork, no different chain. it just means no competition from russia. Cutting the internet connection doesn't take their computational resources. They can still use them to mine blocks, even if they had been using them to provide shares in a pool outside Russia. there was no chain split when kazahkstan went dark last year. because no internet means NO INTERNET I can think of many other reasons why they didn't split Bitcoin. One's that it makes consensus harder to be achieved. Another is that there wasn't enough demand for a fork to occur.
|
|
|
Are you sure that port 3003 is correct? You should set it to the same value as "rest-port" in your c-lightning config. Also, try removing "/v1" as it should not be necessary. Apparently, it's not a port issue, but rather a web socket one. bitcoin@raspibolt:~/.lightning/testnet $ sudo service RTL status ● RTL.service - RTL daemon Loaded: loaded (/lib/systemd/system/RTL.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-03-09 19:21:50 GMT; 47min ago Main PID: 3902 (node) Tasks: 11 (limit: 4915) CGroup: /system.slice/RTL.service └─3902 /usr/bin/node /home/bitcoin/RTL/rtl.js
Mar 09 20:06:49 raspibolt node[3902]: [09/03/2022, 20:06:49] ERROR: CLWebSocket => Web socket error: socket hang up Mar 09 20:06:49 raspibolt node[3902]: [09/03/2022, 20:06:49] INFO: CLWebSocket => Web socket disconnected, will reconnect again.... Mar 09 20:07:53 raspibolt node[3902]: [09/03/2022, 20:07:53] INFO: CLWebSocket => Reconnecting to the CLightning's Websocket Server... Mar 09 20:07:53 raspibolt node[3902]: [09/03/2022, 20:07:53] INFO: CLWebSocket => Connecting to the CLightning's Websocket Server... Mar 09 20:07:53 raspibolt node[3902]: [09/03/2022, 20:07:53] ERROR: CLWebSocket => Web socket error: socket hang up Mar 09 20:07:53 raspibolt node[3902]: [09/03/2022, 20:07:53] INFO: CLWebSocket => Web socket disconnected, will reconnect again.... Mar 09 20:08:57 raspibolt node[3902]: [09/03/2022, 20:08:57] INFO: CLWebSocket => Reconnecting to the CLightning's Websocket Server... Mar 09 20:08:57 raspibolt node[3902]: [09/03/2022, 20:08:57] INFO: CLWebSocket => Connecting to the CLightning's Websocket Server... Mar 09 20:08:57 raspibolt node[3902]: [09/03/2022, 20:08:57] ERROR: CLWebSocket => Web socket error: socket hang up Mar 09 20:08:57 raspibolt node[3902]: [09/03/2022, 20:08:57] INFO: CLWebSocket => Web socket disconnected, will reconnect again.... From a sudo service lightningd status I get: Warning: The unit file, source configuration file or drop-ins of lightningd.service changed on disk. Run 'systemctl daem ● lightningd.service - C-Lightning daemon Loaded: loaded (/lib/systemd/system/lightningd.service; enabled; vendor preset: enabled) Active: activating (start) since Wed 2022-03-09 20:25:31 GMT; 606ms ago Cntrl PID: 9912 (lightningd) Tasks: 13 (limit: 4915) CGroup: /system.slice/lightningd.service ├─9912 /usr/local/bin/lightningd --daemon --conf /home/bitcoin/.lightning/testnet/lightningd.conf --plugin=/h ├─9916 /usr/local/bin/lightningd --daemon --conf /home/bitcoin/.lightning/testnet/lightningd.conf --plugin=/h ├─9917 /usr/local/bin/../libexec/c-lightning/plugins/autoclean ├─9918 /usr/local/bin/../libexec/c-lightning/plugins/bcli ├─9919 /usr/local/bin/../libexec/c-lightning/plugins/fetchinvoice ├─9920 /usr/local/bin/../libexec/c-lightning/plugins/funder ├─9921 /usr/local/bin/../libexec/c-lightning/plugins/topology ├─9922 /usr/local/bin/../libexec/c-lightning/plugins/keysend ├─9923 /usr/local/bin/../libexec/c-lightning/plugins/offers ├─9924 /usr/local/bin/../libexec/c-lightning/plugins/pay ├─9925 /usr/local/bin/../libexec/c-lightning/plugins/txprepare └─9926 /usr/local/bin/../libexec/c-lightning/plugins/spenderp
Mar 09 20:25:31 raspibolt systemd[1]: Starting C-Lightning daemon... Mar 09 20:25:32 raspibolt lightningd[9912]: # Mar 09 20:25:32 raspibolt lightningd[9912]: # Fatal error in , line 0 Mar 09 20:25:32 raspibolt lightningd[9912]: # Check failed: reservation_.SetPermissions(protect_start, protect_size, per Mar 09 20:25:32 raspibolt lightningd[9912]: # Mar 09 20:25:32 raspibolt lightningd[9912]: #FailureMessage Object: 0xbecdb680 So, I'll just blame my luck and reinstall the whole thing unless you've experienced this before.
|
|
|
Is she a fox or a person after all?
|
|
|
[...] Άρα εσύ πρέπει να προστατέψεις τη φράση σου ΚΑΙ τους στίχους από το ποίημα, τουλάχιστον δηλαδή να θυμάσαι ποιο είναι το ποίημα. Εγώ σου προτείνω να κρατήσεις ΜΟΝΟ τη φράση. Για να σου απαντήσω όμως, αν έβρισκα τη φράση σου και γνώριζα επίσης πως την έχεις επεκτείνει με στίχους, το μόνο που μένει είναι να ψάξω όλους τους στίχους. Πόσα ποιήματα υπάρχουν; Λιγότερα από 10 εκατομμύρια. Γενικά προτείνω τα χρήματα να βρίσκονται στο χαρτί, τελεία και παύλα. Αν μπλέξουμε με τη μνήμη του ανθρώπου την κάτσαμε, υπάρχουν πολλά προβλήματα που μπορούν να προκύψουν. Προστατέψτε τις φράσεις σας, δεν είναι τόσο δύσκολο.
|
|
|
Πρέπει να ψάξει στο εύρος των 204812 ή 122048? 2048 12. Αν η φράση αποτελούνταν από μία λέξη, θα ήταν 1 στις 2048. Αν ήταν δύο, θα ήταν 1 στις 2048 2 και πάει λέγοντας.
|
|
|
We won't be able to help you unless you share your config with us. You might have made a small mistake somewhere which causes RTL to use the default settings. { "port": "3000", "SSO": { "rtlSSO": 0, "rtlCookiePath": "", "logoutRedirectLink": "" }, "nodes": [ { "index": 1, "lnNode": "c-lightning", "lnImplementation": "CLT", "Authentication": { "macaroonPath": "/home/bitcoin/c-lightning-REST/certs/" }, "Settings": { "userPersona": "OPERATOR", "themeMode": "NIGHT", "themeColor": "PURPLE", "channelBackupPath": "/home/bitcoin/RTL/", "bitcoindConfigPath": "/mnt/ext/bitcoin/", "logLevel": "INFO", "fiatConversion": false, "lnServerUrl": "https://127.0.0.1:3003/v1" } } ], "multiPassHashed": "80cd7705a67ed19996fac8c8506cf72ac33163cf0fcc60ab0b78462a1f25554d" }
|
|
|
I believe that I also started having problems with the service at some point. I have been running c-lightning-rest as a plugin without any problems since then. You should give it a try. I did, but I have another problem now. Ride The Lightning considers my node as a LND one, but it's C-Lightning and I've written it in RTL-Config.json.
|
|
|
If you want to generate a public key that is valid in secp256k1, then you're limited to its borders; you need it. To find a point in an elliptic curve, you either multiply an already existing starting point (usually referred to as G) with a number, a procedure called Elliptic Curve Multiplication, or add a point to another point, which is called Elliptic Curve Addition. Learn more: https://learnmeabitcoin.com/beginners/public_keys
|
|
|
Οι δώδεκα λέξεις κλειδιά ακόμα και εντελώς στην τύχη να επιλεγούν δεν είναι αρκετά ασφαλές Κάνεις λάθος. Η διαδικασία για να επιλέξει το σύστημα σου 12 λέξεις στην τύχη πάει ως εξής: - Παράγει έναν τυχαίο 128-bit αριθμό.
- Τον κατακερματίζει (με SHA-256) και εισάγει στο τέλος του 4 bits. (το λεγόμενο checksum)
- «Κόβει» αυτά τα 132 bits που έχουν προκύψει σε 12 εντεκάδες. Κάθε εντεκάδα είναι ένας αριθμός από το 0 ως το 2047 (2^11 - 1)
- Αντιστοιχεί κάθε αριθμό σε μία από τις λέξεις ανάλογα με την τιμή του.
Για να βρεί κάποιος την φράση σου πρέπει να ψάξει στο εύρος των 2048 12 διαφορετικών φράσεων. Να σημειωθεί πως η διαδικασία του deriving είναι πιο ισχυρή επεξεργαστικά, καθώς περιέχει διαδικασίες όπως HMAC-SHA256 κλπ, από αυτήν στο brainwallet που απλώς κάνει hash τον κωδικό σου. Θεωρητικά είναι πιο εύκολο να αρχίζεις να ψάχνεις μία μία όλες τις διευθύνσεις, παρά μία μία όλες τις φράσεις 12 λέξεων (με βάση το wordlist πιο πάνω). Εάν οι 12 λέξεις δεν ήταν από μόνες τους ασφαλείς, δεν θα στο πρότεινε κανένα πορτοφόλι.
|
|
|
What's the problem: C-Lightning-REST fails to start. Mar 09 12:14:48 raspibolt node[14132]: --- Starting the cl-rest server --- warn Mar 09 12:14:48 raspibolt node[14132]: --- cl-rest api server is ready and listening on port: 3001 --- warn Mar 09 12:14:48 raspibolt node[14132]: --- cl-rest doc server is ready and listening on port: 4001 --- warn Mar 09 12:15:13 raspibolt node[14132]: Lightning client connection closed, reconnecting error Mar 09 12:15:15 raspibolt node[14132]: Lightning client connection error error Mar 09 12:15:15 raspibolt node[14132]: node:events:504 Mar 09 12:15:15 raspibolt node[14132]: throw er; // Unhandled 'error' event Mar 09 12:15:15 raspibolt node[14132]: ^ Mar 09 12:15:15 raspibolt node[14132]: Error: connect ECONNREFUSED /home/bitcoin/.lightning/testnet/lightning-rpc Mar 09 12:15:15 raspibolt node[14132]: at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) Mar 09 12:15:15 raspibolt node[14132]: Emitted 'error' event on LightningClient instance at: Mar 09 12:15:15 raspibolt node[14132]: at Socket.<anonymous> (/home/bitcoin/c-lightning-REST/lightning-client-js.js:77:23) Mar 09 12:15:15 raspibolt node[14132]: at Socket.emit (node:events:526:28) Mar 09 12:15:15 raspibolt node[14132]: at emitErrorNT (node:internal/streams/destroy:164:8) Mar 09 12:15:15 raspibolt node[14132]: at emitErrorCloseNT (node:internal/streams/destroy:129:3) Mar 09 12:15:15 raspibolt node[14132]: at processTicksAndRejections (node:internal/process/task_queues:83:21) { Mar 09 12:15:15 raspibolt node[14132]: errno: -111, Mar 09 12:15:15 raspibolt node[14132]: code: 'ECONNREFUSED', Mar 09 12:15:15 raspibolt node[14132]: syscall: 'connect', Mar 09 12:15:15 raspibolt node[14132]: address: '/home/bitcoin/.lightning/testnet/lightning-rpc' Mar 09 12:15:15 raspibolt node[14132]: } Mar 09 12:15:15 raspibolt node[14132]: Node.js v17.5.0 Mar 09 12:15:15 raspibolt systemd[1]: c-lightning-REST.service: Main process exited, code=exited, status=1/FAILURE Mar 09 12:15:15 raspibolt systemd[1]: c-lightning-REST.service: Failed with result 'exit-code' I have a Lightning node[1] running fine in testnet and I recently installed Ride The Lightning, which is a comfortable web browser app. After an unfortunate RPi shutdown, I can't understand what have gone wrong, but when I start the service, it prompts me the above. I'm having this issue a week now and I haven't figured out anything despite of all the restarts and re-edits I've done. Everything else (bitcoind, lightningd, tor etc.) works properly.
[1] 032ce2dde49164118420ff73062e4d6c8a155df47251c24fc185e09337c241fd7d@xixzo67fevmab7wytj5qp7mowvbildpbr7xgaj4hp5dbqgr36termcyd.onion:9735
|
|
|
|