Compared with version 0.15.0.1, did 0.15.1 change in any way the caching or disk I/O logic?
No. Only data I can find on the UTXO set shows it's closer to 4GB instead of 8GB. Am I looking at the on-disk size (compressed) compared to the in-memory size? That's the on disk sized which is compressed. The in memory size is much larger, ~7-8GB |
|
|
|
|
It seems that people are incapable of reading. I am locking this thread.
|
|
|
|
|
The Lightning Network has an entire Peer-to-Peer network protocol. Using that protocol, a node can ask its peers for channels that they have open and peers that they know about. Then the node can connect to those other peers (note that connecting does not mean that a channel was opened) and learn of their channels and peers. It can do this to build a graph of the entire network and then thus determine the best route.
Of course there are better ways to do to this with various shortest path algorithms that don't actually need to know the full graph.
|
|
|
|
|
listtransactions is a wallet RPC, it will only give you information about the transactions in your wallet, not the mempool or anything else. The RPC call that you actually want is getrawmempool with the verbose parameter set to true.
|
|
|
|
You DID NOT follow my instructions. If I try Settings>Options>wallet>and then try to open the configuration file> I get the prompt saying that command line options will override this configuration file and GUI settings> but then doesn't know how to open the config file. At that point, I am getting windows "how do you want to open this file prompt.
When I have gone that route in the past I did not get that, it took me straight to the enter command line but now there seems to be something missing.
Choose to open it in notepad. Add the salvagewallet line and save the file. |
|
|
|
|
Please post the debug.log file.
|
|
|
|
May I ask one question? If I create a Segwit wallet on Electrum, can I use that wallet to send/receive bitcoins from Legacy wallets?
Kind of. Electrum jumped straight to using the new Bech32 address format for segwit addresses which only work with wallets that have implemented Bech32 support. There's a trick you can do to get the P2SH nested segwit addresses which are backwards compatible but are still segwit. You can always send to non-segwit addresses. Also, will I be able to use the Lightning Network?
No. You will need to use a software that supports the Lightning Network. |
|
|
|
|
When routing payments, the commitment transactions are updated to reflect the routing. So for Channel 1, A's balance will be 0 BTC and B's will be 2 BTC. For Channel 2, B's balance will be 0 BTC and C's will be 2 BTC. If the commitments are broadcast, A will have 1 less BTC, B will have the same amount, just different outputs, and C will have 1 more BTC. All that happened is that 1 BTC moved from A to B on Channel 1 and 1 BTC moved from B to C on Channel 2.
To guarantee the money transfer, there are actually new outputs created called HTLC outputs. These HTLCs guarantee that all parties will get their money or the route will timeout and the original owners will get their money if the commitments are broadcast. What will usually happen is that the HTLCs are settled off chain once the route is complete but commitments are not actually broadcast. So the values of the respective outputs are merged.
|
|
|
|
You can say that again because Segwit is not implemented for Bitcoin and has been dropped but
it is confusing because I hear about Segwit wallets and I am not talking about Segwit2x here that uses B2X
This is strictly untrue. Segwit as specified by BIPs 141, 143, and 144 is activated on Bitcoin. The original segwit2x proposal is not and is dead. Segwit is absolutely implemented for Bitcoin and was not dropped. |
|
|
|
Also, if I am to start bitcoin core with -salvagewallet can I do that thru the RPC console
No, it is not an RPC command. You can't start Bitcoin Core with that option through Bitcoin Core's RPC console. or do I run bitcoind and do it from there?
No need to use bitcoind or any RPC command. Go to Help > Debug Window and click the button to open the bitcoin.conf file. Add the following line: Restart Bitcoin Core. Once it has restarted, you will want to remove that line from the bitcoin.conf file otherwise it will attempt to salvage your wallet every time you start Core, which is bad. If I am understanding you it would seem that the salvagewallet command should be given before startup? Which would be bitcoin-cli or bitcoind perhaps?
Again, it is not a command, it is a startup option. I don't have a backup wallet dat file from before this all started to take place unless bitcoin core does periodic backups on it's own which it probably does not.
It does not make backups automatically. |
|
|
|
How do I copy it into the new version of Bitcoin Core?
Copy and paste the file into the Bitcoin Core datadir. Is Bitcoin Core backward-compatible this far back? will my wallet work in the new version?
Yes, Bitcoin Core is completely backwards compatible. I should add that I only have the file. I do not have the private key, so I can't sweep it into another wallet.
The wallet.dat file contains your private keys. |
|
|
|
|
Account for what? There are no such things as "Bitcoin accounts". You have you account with a service; what service did you use? Obviously you will need to know what the username and password are, assuming that the service still even exists.
|
|
|
|
Yup, looks like it works. I got to protoc.exe --proto_path=./ --python_out=./ ./paymentrequest.proto where it came back with :
PS E:\Downloads\achow tool\payment-proto-interface-master> protoc.exe --proto_path=./ --python_out=./ ./paymentrequest.p
roto
protoc.exe : The term 'protoc.exe' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ protoc.exe --proto_path=./ --python_out=./ ./paymentrequest.proto
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (protoc.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command protoc.exe was not found, but does exist in the current location. Windows PowerShell
does not load commands from the current location by default. If you trust this command, instead type: ".\protoc.exe". S
ee "get-help about_Command_Precedence" for more details.
PS E:\Downloads\achow tool\payment-proto-interface-master>
... Ok. Try ./protoc.exe --proto_path=./ --python_out=./ ./paymentrequest.proto
|
|
|
|
|
Hmm. That error number might actually mean that your wallet is corrupted.
First stop Bitcoin Core and make a backup of your wallet.dat file.
If you have an older backup of your wallet, try restoring that backup.
Otherwise start Bitcoin Core with -salvagewallet and report back with what happens.
|
|
|
|
Umm, no. That's completely wrong. Electrum supports segwit out of the box. When you create a wallet, there is an option for Legacy or Segwit. Choosing Segwit lets you use bech32 addresses. It's super easy. For Bitcoin Core, once 0.16.0 is released, it will use p2sh wrapped segwit by default. |
|
|
|
error: Could not find suitable distribution for Requirement.parse('pyqt5')
Friggin pyqt. Do and then run the other commands again. |
|
|
|
If you give me the steps to build from source using python, I'll give that a whirl.
To run from source, first download and install python from https://www.python.org/. There's a section where it says something about adding python to your PATH, make sure you choose that option. Downlaod and extract protoc from https://github.com/google/protobuf/releases. There should be a file named protoc.exe in the bin folder. Download the code from https://github.com/achow101/payment-proto-interface. Copy protoc.exe from the previous step into the folder containing the source code. Open up a command prompt or powershell in the folder with the source code. Then run the following commands: python setup.py install
protoc.exe --proto_path=./ --python_out=./ ./paymentrequest.proto
Then run the cli program using or the gui program using |
|
|
|
|
If you don't use Segwit or Armory's P2SH-P2PK address options (may not be present in 0.96), Then there will be no incompatibility.
|
|
|
|
there is no ETA. lightning developers have taken the position that there is "no rush" considering how much value is expected to be stored in payment channels. they are very concerned about ensuring that no funds are lost as a result of using the LN protocol.
having said that, it's pretty widely expected that LN will be usable by the general public sometime this year, likely in a matter of months. the next major step is to complete wallet implementations. we're already seeing lightning transactions on the network; now it's mainly just a matter of releasing the software.
It's not like there's an actual "official LN launch" date or anything like that. Rather LN will be "launched" when people feel confident enough in one or more implementations of LN to use it on the main Bitcoin network. In fact, you could consider LN to already be launched as there already are people using LN on the mainnet. Of course those people do so at the risk of their money, but nonetheless, the software mostly works and there are transactions occurring. I wonder how a Lightning user interface would look like. Instead a "Send" button there will be "Open channel" button (same fee as just Send button + X bitcoins to deposit into channel) and then "Send via the opened channel" (no fee) and then "Close channel" (same fee as just Send button). Given this complexity and the fact that you have to spend twice as much in fees to send same amount of money as without LN I really wonder how the "greed" would work.
It's very likely that it will still just be a "Send" button. Channel management and all that will actually be handled by the software automatically. You put money into your LN wallet, and it will use that to open and close channels automatically. So when you want to send Bitcoin to someone, your LN wallet will have established several channels. It will also determine an optimal route and do everything automatically for you. There's no need for you to manually open and close channels yourself; the software will handle all of that for you. |
|
|
|
|
Show Posts
