|
Which file contains the keys that grant me access to the channel? I have opened one private channel with my main node, worth of 300,000 sats. I've sent 150,000 sats, to make it balance, but I now want to empty it and retry, from a brand new node. Is it lightningd.sqlite3?
I have renamed ./lightningmobile/bitcoin to ./lightningmobile/bitcoin2, ran lightningd again, and it created a new bitcoin directory. The "Server started with public key x" appeared, but it currently has 0 channels. So, the access to the channel must be at bitcoin2. Note that the lightning-rpc isn't located at ./lightningmobile, but at ./lightningmobile/bitcoin for some reason I don't understand.
---------------
I'm far away from home and do everything with SSH via Tor. It goes so slowly...
|
|
|
|
No, it doesn't work that way, if everyone would replace a gear rated 300W and 100th/s with one rated 3000w and 200th/s the consumption will not grow, the margin rate will neither since you get the same share for the same cost, the hash rate will go up but without increased energy needs. Right, the energy required per bitcoin does not change based on difficulty. What does change, based on it, is the hashes required per bitcoin. But there isn't a strict correlation between the cost of joule and the cost of calculating a hash. Small contradiction there. If using the same amount of energy, the energy required per bitcoin would be the same and would not increase. Let me rephrase: If using the same amount of energy, all miners upgraded to more efficient devices, difficulty would increase and, therefore, so would the hashes per bitcoin. So, what does change (specifically decreases) when mining becomes more efficient is the energy required to calculating 1 hash. |
|
|
|
Bitcoin energy consumption depends primarily on the cost of energy and the value of the block reward, and efficiency affects neither of those. Not sure if I understand this sentence. Isn't efficiency strictly correlated with the cost? If you find a more efficient way to calculate the hashes, it means you've found a cheaper way. If using the same amount of energy, all the miners upgraded to more efficient devices, difficulty would increase and, therefore, so would the energy required per bitcoin (AKA, energy consumption). |
|
|
|
@BlackHatCoiner, does when you start the node, the debug show any output that starts with "Server started with public key xxx"? No. I'm running two SSH sessions right now, one with lightningd and another with tail-ing the debug.log. 1: bitcoin@raspibolt:~ $ lightningd --conf=/home/bitcoin/.lightningmobile/lightningd.conf --lightning-dir=/home/bitcoin/.lightningmobile
(stuck here) 2: bitcoin@raspibolt:~ $ sudo tail -f /home/bitcoin/.lightningmobile/debug.log
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 723785x2343x1/1 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 741095x1126x0/1 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 741095x1031x1/1 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 738602x974x1/0 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 741095x541x0/1 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 710043x428x0/1 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 738602x969x1/1 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 731109x1119x0/0 now ACTIVE
2022-07-17T18:36:04.267Z DEBUG gossipd: Received channel_update for channel 716516x843x0/0 now ACTIVE
2022-07-17T18:36:04.268Z DEBUG gossipd: REPLY WIRE_GOSSIPD_INIT_REPLY with 0 fds
2022-07-22T17:57:29.684Z DEBUG lightningd: Opened log file /home/bitcoin/.lightningmobile/debug.log
2022-07-22T17:57:29.684Z DEBUG lightningd: Opened log file /home/bitcoin/.lightningmobile/debug.log
2022-07-22T17:57:29.693Z DEBUG plugin-manager: started(23544) /usr/local/bin/../libexec/c-lightning/plugins/autoclean
2022-07-22T17:57:29.701Z DEBUG plugin-manager: started(23545) /usr/local/bin/../libexec/c-lightning/plugins/bcli
2022-07-22T17:57:29.710Z DEBUG plugin-manager: started(23546) /usr/local/bin/../libexec/c-lightning/plugins/fetchinvoice
2022-07-22T17:57:29.718Z DEBUG plugin-manager: started(23547) /usr/local/bin/../libexec/c-lightning/plugins/funder
2022-07-22T17:57:29.751Z DEBUG plugin-manager: started(23548) /usr/local/bin/../libexec/c-lightning/plugins/topology
2022-07-22T17:57:29.768Z DEBUG plugin-manager: started(23549) /usr/local/bin/../libexec/c-lightning/plugins/keysend
2022-07-22T17:57:29.792Z DEBUG plugin-manager: started(23550) /usr/local/bin/../libexec/c-lightning/plugins/offers
2022-07-22T17:57:29.812Z DEBUG plugin-manager: started(23551) /usr/local/bin/../libexec/c-lightning/plugins/pay
2022-07-22T17:57:29.838Z DEBUG plugin-manager: started(23552) /usr/local/bin/../libexec/c-lightning/plugins/txprepare
2022-07-22T17:57:29.852Z DEBUG plugin-manager: started(23553) /usr/local/bin/../libexec/c-lightning/plugins/spenderp
2022-07-22T17:57:30.013Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_channeld
2022-07-22T17:57:30.038Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_closingd
2022-07-22T17:57:30.072Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_connectd
2022-07-22T17:57:30.101Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_gossipd
2022-07-22T17:57:30.129Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_hsmd
2022-07-22T17:57:30.157Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_onchaind
2022-07-22T17:57:30.193Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_openingd
2022-07-22T17:57:30.224Z DEBUG hsmd: pid 23562, msgfd 39
2022-07-22T17:57:30.774Z DEBUG connectd: pid 23563, msgfd 43
2022-07-22T17:57:30.775Z DEBUG hsmd: new_client: 0
2022-07-22T17:57:30.875Z DEBUG connectd: Proxy address: 127.0.0.1:9050
2022-07-22T17:57:30.875Z DEBUG connectd: Created IPv4 listener on port 9835
2022-07-22T17:57:30.876Z DEBUG connectd: REPLY WIRE_CONNECTD_INIT_REPLY with 0 fds
2022-07-22T17:57:30.880Z DEBUG gossipd: pid 23564, msgfd 42
2022-07-22T17:57:30.881Z DEBUG hsmd: new_client: 0
2022-07-22T17:57:35.826Z DEBUG gossipd: gossip_store_compact_offline: 0 deleted, 22662 copied
2022-07-22T17:57:35.826Z DEBUG gossipd: Received channel_update for channel 738586x899x1/1 now ACTIVE
2022-07-22T17:57:35.831Z DEBUG gossipd: Received channel_update for channel 738586x1081x1/1 now ACTIVE
2022-07-22T17:57:35.831Z DEBUG gossipd: Received channel_update for channel 739408x2208x0/1 now ACTIVE
2022-07-22T17:57:35.832Z DEBUG gossipd: Received channel_update for channel 731109x938x1/0 now ACTIVE
2022-07-22T17:57:35.832Z DEBUG gossipd: Received channel_update for channel 700393x896x0/0 now ACTIVE
2022-07-22T17:57:35.832Z DEBUG gossipd: Received channel_update for channel 718348x836x0/0 now ACTIVE
2022-07-22T17:57:35.832Z DEBUG gossipd: Received channel_update for channel 737921x1833x0/0 now ACTIVE
2022-07-22T17:57:35.832Z DEBUG gossipd: Received channel_update for channel 724642x918x1/0 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 741095x1108x0/1 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 736890x1413x0/1 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 723785x1459x1/0 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 723785x2343x1/1 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 741095x1126x0/1 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 741095x1031x1/1 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 738602x974x1/0 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 741095x541x0/1 now ACTIVE
2022-07-22T17:57:35.833Z DEBUG gossipd: Received channel_update for channel 710043x428x0/1 now ACTIVE
2022-07-22T17:57:35.834Z DEBUG gossipd: Received channel_update for channel 738602x969x1/1 now ACTIVE
2022-07-22T17:57:35.834Z DEBUG gossipd: Received channel_update for channel 731109x1119x0/0 now ACTIVE
2022-07-22T17:57:35.834Z DEBUG gossipd: Received channel_update for channel 716516x843x0/0 now ACTIVE
2022-07-22T17:57:35.834Z DEBUG gossipd: REPLY WIRE_GOSSIPD_INIT_REPLY with 0 fds
I'm not sure about this, but in one of those 2 stackexchange links I sent in a few posts above, someone says that we have to set different ports for RPC. It did work at first. Then, it suddenly stopped working. I've had my two lightning nodes running for a few minutes. Besides, they already do listen to different ports. (9735, 9835) Easiest way to confirm that ports are the issue would be to shut down the main Core Lightning node and then start the lightningmobile one. Tried it. The issue wasn't resolved. The mobile node couldn't startup. |
|
|
|
|
Απίστευτο πόσα πράγματα γίνονταν τόσο καιρό και δεν τα καταλάβαινα. Τώρα αρχίζει να βγάζει νόημα όλη αυτή η σκαμδημία.
|
|
|
|
Take this shit seriously, and don't propose changes just to soothe your ego. You're here since 2011 and you've yet to understand that making discussion, proposing changes and producing consensus is what take the cake? We soothe no ego, and even if we do, that's how it works, sorry. Bitcoin was not discovered. It was invented, and whatever is invented by a person can also be changed, recreated, molded by a person. We need none of your permission to do it. There's no such thing as democracy in this system. You're the one who's, crucially, responsible for your monetary policy, and who's an economic resource for those who follow that same policy. You don't gain this shit elsewhere. That's why it's so valuable. We have a problem. We seek for a solution. You're free to disapprove it, and if the overwhelming majority acts likewise, then it's likely not a viable solution. But, discussion needs to be made, to reach to a conclusion. Otherwise your ecosystem might falter on its own. Granted, tail emission or any other change in mining economics cut no ice, but acknowledge that the system's security might be at some crisp risk in the future. |
|
|
|
|
“No amount of evidence will ever persuade an idiot.” – Mark Twain
How about we leave it there?
|
|
|
|
Over inflation of merit source and merit source allocation can create a new generation of pseudo-quality members who will turn to likely spammers after ranking up. It still requires to somewhat prove you're a quality writer, with or without merit inflation. You can't just reach 100, 250 or 500 merits, whether we have 111 or a thousand merit sources. That's why most bounty hunters remain with less than 100. The recent merit inflation did more good with the entrance of new, merit-worthy users than bad for these few merit whores. |
|
|
|
bitcoin@raspibolt:~ $ lightningd --lightning-dir=/home/bitcoin/.lightningmobile > /dev/null 2>&1 &
[1] 14287
bitcoin@raspibolt:~ $ lightning-cli --lightning-dir=/home/bitcoin/.lightningmobile getinfo
lightning-cli: Connecting to 'lightning-rpc': Connection refused
[1]+ Exit 1 lightningd --lightning-dir=/home/bitcoin/.lightningmobile > /dev/null 2>&1 |
|
|
|
Any command without " --lightning-dir=/home/bitcoin/.lightningmobile" works properly, because it refers to my main node. By default, if you don't specify a lightning-dir, it'll be " /.lightning". The problem is with the .lightningmobile node. That's my configuration: bitcoin@raspibolt:~ $ sudo cat /home/bitcoin/.lightningmobile/lightningd.conf
daemon
alias=Lightning Vortex from mobile
network=bitcoin
log-level=debug
log-file=/home/bitcoin/.lightningmobile/debug.log
# incoming via tor
bind-addr=127.0.0.1:9835
announce-addr=rbfwzvypteyncgwr2iywyvt7k3vbga7hzuemtkoinivlz5tr2ofzv7yd.onion
# outgoing via tor
proxy=127.0.0.1:9050
always-use-proxy=true I doubt it helps.
bitcoin@raspibolt:~ $ lightning-cli --lightning-dir=/home/bitcoin/.lightningmobile getinfo
lightning-cli: Connecting to 'lightning-rpc': Connection refused bitcoin@raspibolt:~ $ lightningd --conf=/home/bitcoin/.lightningmobile/lightningd.conf --lightning-dir=/home/bitcoin/.lightningmobile
----
(stuck doesn't do anything)
That's the output: bitcoin@raspibolt:~ $ ps aux | grep lightningd
bitcoin 4652 3.8 0.2 21928 9820 pts/3 D 19:36 0:03 lightningd --conf=/home/bitcoin/.lightningmobile/lightningd.conf --lightning-dir=/home/bitcoin/.lightningmobile
bitcoin 5814 6.1 2.2 100256 88640 ? Ds 17:25 8:04 lightningd --conf=/home/bitcoin/.lightning/lightningd.conf
bitcoin 6665 0.0 0.0 4916 532 pts/3 S+ 19:37 0:00 grep --color=auto lightningd
|
|
|
|
Or I just use the cat command: bitcoin@raspibolt:~ $ sudo cat /home/bitcoin/.lightningmobile/debug.log
2022-07-17T18:07:03.423Z DEBUG lightningd: Opened log file /home/bitcoin/.lightningmobile/debug.log
2022-07-17T18:07:03.423Z DEBUG lightningd: Opened log file /home/bitcoin/.lightningmobile/debug.log
2022-07-17T18:07:03.429Z DEBUG plugin-manager: started(31634) /usr/local/bin/../libexec/c-lightning/plugins/autoclean
2022-07-17T18:07:03.436Z DEBUG plugin-manager: started(31635) /usr/local/bin/../libexec/c-lightning/plugins/bcli
2022-07-17T18:07:03.442Z DEBUG plugin-manager: started(31636) /usr/local/bin/../libexec/c-lightning/plugins/fetchinvoice
2022-07-17T18:07:03.450Z DEBUG plugin-manager: started(31637) /usr/local/bin/../libexec/c-lightning/plugins/funder
2022-07-17T18:07:03.462Z DEBUG plugin-manager: started(31638) /usr/local/bin/../libexec/c-lightning/plugins/topology
2022-07-17T18:07:03.481Z DEBUG plugin-manager: started(31639) /usr/local/bin/../libexec/c-lightning/plugins/keysend
2022-07-17T18:07:03.501Z DEBUG plugin-manager: started(31640) /usr/local/bin/../libexec/c-lightning/plugins/offers
2022-07-17T18:07:03.521Z DEBUG plugin-manager: started(31641) /usr/local/bin/../libexec/c-lightning/plugins/pay
2022-07-17T18:07:03.541Z DEBUG plugin-manager: started(31642) /usr/local/bin/../libexec/c-lightning/plugins/txprepare
2022-07-17T18:07:03.561Z DEBUG plugin-manager: started(31643) /usr/local/bin/../libexec/c-lightning/plugins/spenderp
2022-07-17T18:07:03.705Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_channeld
2022-07-17T18:07:03.723Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_closingd
2022-07-17T18:07:03.741Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_connectd
2022-07-17T18:07:03.759Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_gossipd
2022-07-17T18:07:03.777Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_hsmd
2022-07-17T18:07:03.796Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_onchaind
2022-07-17T18:07:03.814Z DEBUG lightningd: testing /usr/local/libexec/c-lightning/lightning_openingd
2022-07-17T18:07:03.833Z DEBUG hsmd: pid 31651, msgfd 39
2022-07-17T18:07:04.097Z DEBUG connectd: pid 31652, msgfd 43
2022-07-17T18:07:04.098Z DEBUG hsmd: new_client: 0
2022-07-17T18:07:04.188Z DEBUG connectd: Proxy address: 127.0.0.1:9050
2022-07-17T18:07:04.188Z DEBUG connectd: Created IPv4 listener on port 9835
2022-07-17T18:07:04.188Z DEBUG connectd: REPLY WIRE_CONNECTD_INIT_REPLY with 0 fds
2022-07-17T18:07:04.191Z DEBUG gossipd: pid 31653, msgfd 42
2022-07-17T18:07:04.191Z DEBUG hsmd: new_client: 0
2022-07-17T18:07:05.555Z DEBUG gossipd: gossip_store_compact_offline: 0 deleted, 22662 copied
2022-07-17T18:07:05.555Z DEBUG gossipd: Received channel_update for channel 738586x899x1/1 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 738586x1081x1/1 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 739408x2208x0/1 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 731109x938x1/0 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 700393x896x0/0 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 718348x836x0/0 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 737921x1833x0/0 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 724642x918x1/0 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 741095x1108x0/1 now ACTIVE
2022-07-17T18:07:05.556Z DEBUG gossipd: Received channel_update for channel 736890x1413x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 723785x1459x1/0 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 723785x2343x1/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 741095x1126x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 741095x1031x1/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 738602x974x1/0 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 741095x541x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 710043x428x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 738602x969x1/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 731109x1119x0/0 now ACTIVE
2022-07-17T18:07:05.558Z DEBUG gossipd: Received channel_update for channel 716516x843x0/0 now ACTIVE
2022-07-17T18:07:05.558Z DEBUG gossipd: REPLY WIRE_GOSSIPD_INIT_REPLY with 0 fds
Doesn't it seem anything wrong in here. |
|
|
|
I removed the already existent debug.log, ran daemon with --log-level=debug and this is what I get: bitcoin@raspibolt:~ $ tail -f /home/bitcoin/.lightningmobile/debug.log
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 723785x2343x1/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 741095x1126x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 741095x1031x1/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 738602x974x1/0 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 741095x541x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 710043x428x0/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 738602x969x1/1 now ACTIVE
2022-07-17T18:07:05.557Z DEBUG gossipd: Received channel_update for channel 731109x1119x0/0 now ACTIVE
2022-07-17T18:07:05.558Z DEBUG gossipd: Received channel_update for channel 716516x843x0/0 now ACTIVE
2022-07-17T18:07:05.558Z DEBUG gossipd: REPLY WIRE_GOSSIPD_INIT_REPLY with 0 fds
Using screen What's the difference with screen? I don't have this command. |
|
|
|
[...] I have a little problem with this. It worked, I did setup a second lightning node, I did make it connect with my mobile phone (using zeus), but it has now stopped working. I run: lightningd --conf=/home/bitcoin/.lightningmobile/lightningd.conf --lightning-dir=/home/bitcoin/.lightningmobile And it just lags. It isn't running, because I run getinfo and this is what I get: bitcoin@raspibolt:~ $ lightning-cli --lightning-dir=/home/bitcoin/.lightningmobile getinfo
lightning-cli: Connecting to 'lightning-rpc': Connection refused I've killed the process, retried, nothing. I've also rebooted. My main node (from the default directory) works fine: bitcoin@raspibolt:~ $ lightning-cli getinfo
{
"id": "03cd32110547654132187f08e217b20e3ce69f49dff5119da5597a5c0f8a2c7a5e",
"alias": "Lightning Vortex",
"color": "03cd32",
"num_peers": 11,
"num_pending_channels": 0,
"num_active_channels": 11,
"num_inactive_channels": 0,
"address": [
{
"type": "torv3",
"address": "xixzo67fevmab7wytj5qp7mowvbildpbr7xgaj4hp5dbqgr36termcyd.onion",
"port": 9735
}
],
"binding": [
{
"type": "ipv4",
"address": "127.0.0.1",
"port": 9735
}
],
"version": "v0.10.2",
"blockheight": 745385,
"network": "bitcoin",
"msatoshi_fees_collected": 16898,
"fees_collected_msat": "16898msat",
"lightning-dir": "/home/bitcoin/.lightning/bitcoin"
} Edit: One thing that's weird is that from above, you can see that it says "num_active_channels": 11, but from RTL, there are 10 active, and 1 inactive, which is right, because my second node is offline. Edit #2: Whoever helps me fix it gets 9,001 Lightning sats.  |
|
|
|
What do you think about the bigger interest from the people of a country that has a big inflation rate? What could I say? They must have observed something going wrong with their economy, their national currency is seriously devaluated. There's definitely a decent number of Turkish who're obsessed with using a neutral currency that does not represent a country, whose inflation schedule is programmed. Do you think that it stems from the desire that people want to keep the values of things they have? I don't understand what you mean here. Or is it easier to take risks for these people in countries like this? It is easier to distrust the word of politicians, in cases like Turkey. |
|
|
|
It is not fair for people years ago This is the same as saying "It's not fair to rise the price of coffee, because it costed less a year ago" or "It's not fair to pay 100,000 sats for a product, because some people four years ago paid 0.01 BTC for it". In both cases, it's not the merchant's fault; it's just the nature of inflation/deflation. Merit sources are more than they were few years ago. sMerits have increased. It's natural, therefore, to reward more generously. |
|
|
|
Judging by your other thread, it seems that you're trying to give a solution to an XY problem. What are you trying to accomplish? I can't think of one reason you'd need to import the same public key thrice with different address types each time, and then spend these three outputs. |
|
|
|
With bitcoin - there is no company, there are no employees, there is no product, no revenues and no profits. Exactly - though, there are unrealized gains - that's the way bitcoin works. There are no costly intermediaries which make it work less efficiently, because there's no product/service either. The value they say is "the network itself that is growing exponentially". Digits on a computer masquerading as digital assets for a group of people looking to get rich quick or motivated by a strong distrust of the fiat money system. And it works. We've collectively decided that it's a form of money, and it works like a charm. There's motivation to be responsible for your monetary policy. It's a brand you thing; something you couldn't gain before. There's an alternative monetary system, whose usage isn't now more being forced. We can either use it or not use it, as we please. We believe that power comes with monetary control. We reasonably evaluate this. There are profits to be made pushing the bitcoin narrative - and an entire industry has grown up around it. Rather, an entire economy. Only one problem: look closely and the network itself has to be accessed through a series of gates (physical & political) that that are outside the control of the network. The network can be accessed by either the clear net, the Tor network, the i2p network, using the TCP/IP protocol. It can also be accessed via satellite. The network's units (bitcoins) can be acquired using either centralized, decentralized exchanges or no exchanges at all. |
|
|
|
Miners have a collective incentive not to drop their minimum fee rate and cash in in the short term so as not to jeopardize their future profits. So, why 1 sat/vb? Why don't they have it at 10 sat/vb? This should supposedly drop some of their short term profit and rise their long term profit. What did change in v0.8.2 and they lowered the limit from 50,000 sat/kb to 10,000 sat/kb? Let alone in earlier versions. Answer: Demand. If the miners decided the minimum relay fee, it wouldn't be called "relay fee". The full nodes decide that, hereby the users. If you run bitcoin-cli getpeerinfo you might see some peers who've set their minfeefilter to 0.00000000. I'm connected with one. |
|
|
|
Φέρτε 10k να γεμίσουμε τσάντες!  Εγώ πάλι προβλέπω άνοδο, γιατί δε μιλάει κανείς στο adslgr.  Όπως και να' χει, κάνουμε σοβαρό DCA αυτές τις μέρες. |
|
|
|
|
Show Posts
