 Show Posts
|
|
Pages: [1]
|
|
bitcoin-cli -rpcwallet="" getwalletinfo
{
...
"format": "sqlite",
...
"descriptors": true,
...
}
Seems like it migrated, right?
|
|
|
|
I shut down bitcoin-qt. When I started it again, it started with some bitcoin-25.99* version, and no wallet was loadable. It was only a node with peers, nothing else.
It sounds like you compiled it from source and did so without wallet support enabled. You probably didn't have the wallet dependencies installed in a way that the build could find them, so it didn't build the wallet component. if you want to use bitcoind, it should already come with the bitcoin-qt that you already have. They are released together. Regardless, there is no difference between the functionality of bitcoind and bitcoin-qt, except that bitcoin-qt has a GUI. The RPCs all behave the same way. What happens if you just wait longer for the migration to finish? Nice. I tried bitcoind again. This time, I loaded it from the same folder as bitcoin-qt and gave it the same permission: cd '/(localpath)/bitcoin-25.0/bin' chmod +x bitcoind ./bitcoind In another terminal I tried: bitcoin-cli getbalance It returned a different error: error code: -19 error message: Wallet file not specified (must request wallet RPC through /wallet/<filename> uri-path). Try adding "-rpcwallet=<filename>" option to bitcoin-cli command line. So I did as instructed: bitcoin-cli -rpcwallet="" getbalance It worked. I will write bitcoin-cli -rpcwallet="" from now on I guess. I think I'm going to wait for more bugs get fixed and a migration button to be added to the UI before I do it. Thanks. |
|
|
|
Is your wallet large? Does it have a lot of addresses and transactions? Have you done anything atypical with your wallet such as importing scripts and pubkeys?
The migration process shouldn't take too long, although it can take some time depending on the size of your wallet since it has to rewrite everything to a new file.
It's possible that there is a bug somewhere, although it may be hard to diagnose that without access to the wallet itself.
Wallet is about 2^6 transactions and about the same number of receiving addresses. I haven't tried to import scripts or pubkeys, but in the last days I tried to install the Berkeley DB dependencies to run bitcoind from the terminal (on a Ubuntu PC). bitcoind still couldn't load my wallet. Everything worked fine with bitcoin-qt UI. NEW: I reloaded my backup wallet. I saw my transactions and balance again but I did not send nor receive. I shut down bitcoin-qt. When I started it again, it started with some bitcoin-25.99* version, and no wallet was loadable. It was only a node with peers, nothing else. I resinstalled bitcoin-25.0 and finally I could access my wallet again. I successfully made a new transaction with it. It says "*.legacy.bak". Migration apparently didn't work. At that point I'm just too afraid to try migratewallet again. I don't want to end up with a corrupted wallet file. I'd really want to use bitcoind though but it doesn't seem possible with a legacy wallet. |
|
|
|
|
As the title say.
RPC returned "Éxécution..." and then nothing. After ten minutes I reopened the backup wallet.
Wallet has no name (I put "" in the parameter). I gave it a name when I first used Bitcoin Core in 2016 but somehow it got lost along the way with new versions. Passphrase and interface are French.
Should I wait it gets fixed or it could be done now? I want to migrate from Berkeley DB to sqlite. Not sure if it's legacy or descriptors.
|
|
|
|
This deal might have already been settled?
If not, I guess a transaction will be finalized first before funds and goods are actually sent. The full payable amount in BTC will be agreed before the buyer will send the full payment through a trusted escrow agreed by both parties. There may actually be no need for an advance.
I had proposed a price in BTC based on the best estimate of the cost of the product + cost of shipping + my own service fee, and I would have covered any unexpected variation. I had found an escrow and wrote an agreement in which the buyer would have covered the escrow fee, Bitcoin network transaction fees, and any custom tax in his country. The buyer did not go forward with the deal after that point. |
|
|
|
Never transact anything unless the money is received via escrow, the buyer looks really suspicious i mean why would he need to contact an individual if there are tons of services online that offers the same task you're doing and out of all people why did he only chose you to contact, cause according to your story it seems to me that he's just a random stranger that contacted you.
He saw my previous post. He's looking for a local product and to buy it with BTC. I don't see any problem as long as a reputable escrow is used. |
|
|
|
Anyway, the seller should be able to do a trick, like increase the estimation shipping cost or the actual price to replace the deposit.
Looks like that. I'm going to charge my own fee for my service, and I'll absorb unexpected shipping costs and Bitcoin price fluctuations. Shipping cost is not the only problem for you, sometimes the products won't get approved by customs if its send by someone personal on particular country so you need to analyse the receiving country's laws as well before making an estimation because he might say that he didn't receive anything so asking for payback from escrow.
Customs shouldn't be a problem. Product is legal. It's not heavy; it fits in a regular mail package. I think any possibility of surprised custom costs should be paid by the buyer and it should be agreed upon with the escrow. I'm still at the stage of looking for an escrow now. Just saying. |
|
|
|
|
I've been contacted by someone in another country (B) who wants a product from the country where I live (A). He would pay me in BTC to buy the product and ship it to him.
I want to make an estimation of the price of the product + price of shipping, add a deposit %, and divide by an estimation of Bitcoin price in A's currency, to know how much Bitcoin he should send to an escrow at first. Then I'd buy the product, ship it, and I'd take Bitcoin's price at the time of both events, to know how much it really costed. Then the escrow could send me the real price in BTC, and the difference back to the buyer in country B.
But the buyer insists there is no need for a deposit, that using an escrow is enough. The problem is I don't know the exact price of the shipping until I'm at the post office with the product already purchased ready to be sent, and we don't know what the price of Bitcoin in A's currency will be at the time of purchase. There could be a day or two between the time he sends Bitcoin to the escrow, and the time the product is bought.
If you are used to do this, what's the usual, safe way?
|
|
|
|
In person. For cash for whatever price listed on taiwanese exchange at the time. Open to other payment methods after first meeting. Don't hesitate to contact me even years after this post. email: q8hd.ski4.968a.vqfu@yandex.comTelegram: https://t.me/Btcrdba |
|
|
|
- Why are you paying for windows if you don't want it?
I specify to the vendors that I do not want Windows whatsoever. I do not pay for it. But I can't be sure it wasn't ever installed on my product in the past. - Why are you purchasing from a vendor that you think is going to install a backdoor in your PC's hardware?
Vendors are just guys who purchase hardware from suppliers and build PCs for clients. Even if I have a good relationship with a vendor it doesn't mean I'm sure about the reliability of every hardware piece. That's why I specified the specs of the PC I intend to buy, and the fact I live in Taiwan, because I wouldn't trust anything made in mainland China, but I know Taiwan exports processors to the whole world. - I recommend getting a larger SSD if you want to store the whole blockchain on it. If you intend to enable pruning then you don't need a large SSD but if you don't then I suggest getting a 1TB one. You will want to store the whole blockchain if you intend to add/remove wallets regularly. Syncing the blockchain on a hard drive will take longer so you need the SSD for that.
Thanks for the suggestion I really appreciate. |
|
|
|
|
Good to know. I'll go on with it.
|
|
|
|
Noob question: I am planning to buy a new desktop PC and to store bitcoin on Bitcoin Core Desktop Wallet full node. I am currently doing that on my laptop. I bought it from ZaReason, it's tailor made designed to run linux. Now I moved to Taiwan and don't want to import from abroad, since so much hardware is produced here. Knowing that - I'd format the hard drive to get rid of preinstalled Windows OS
- I'd get these specs:
Do you think there is any possibility of hardware backdoor, or any leftovers from Windows, that would put my bitcoin at risk? I plan to use it as my main, home workstation. |
|
|
|
|
You were both right. The error lied in the softwares I was using: wolfram mathematica and libreoffice calc. It seems that for floating numbers greater than 1, the number of digits after decimal point is rounded to six, hence the difference. There is no problem for amounts lower than 1.
Thanks.
|
|
|
|
Hello. First time poster but long time lurker. This might be a noob question... By 'Large Transaction' I mean large number of inputs and outputs. I'm looking into Wasabi CoinJoins on Blockchain explorers and there's something I don't understand: There is a slight difference between, on one hand the total btc input minus the total btc output, and on the other hand, the displayed miner fee. For example in this transaction: https://blockchair.com/bitcoin/transaction/e9abc669f19439f7f738e26516106d74ddfc8ff761ce6e718dc9479392a05dfbThe displayed total input is 81.26491943, total output is 81.26462135, and miner's fee is 0.00029808. But if I click on the 'Raw transaction' button and add up all outputs from the JSON code, I get a total of 81.26462131. There's a 4 satoshis difference. The transaction is displayed the same way on a few blockchain explorers. I also saw the same problem with other large transactions. Where is the problem? Thanks. |
|
|
|
|
