Most likely because it is the "M1"... which isn't using an x86 chipset... but is ARM based. No doubt there are a lot of incompatibilities with various libraries etc. Unless you can run an emulator on it, I don't fancy your chances of getting it working...  |
|
|
|
|
There is no guarantee that sending a transaction for the same (or slightly lower) amount as the UTXO you're trying to "isolate" will even use that particular UTXO... unless it is the only UTXO in your wallet.
If you don't have coin control options, then you're at the mercy of whatever algorithm/stragey the wallet devs use to pick UTXOs... which could be any one of:
- First in, First Out (spend oldest)
- Last in, First Out (spend newest)
- Random
- Minimum change produced
- Closest match
- Spend all
etc...
Unless you know exactly how the wallet is going to select UTXOs... attempting to do a 1 sat/byte transaction in the hopes of "isolating" this UTXO could prove to be a waste of time and btc.
|
|
|
|
In electrum i've done the pass phrase and standard wallet with legacy and 12 derivations.
This doesn't sound right... and I'm confused as to what you actually did... the correct sequence is: Standard Wallet -> Use a Hardware Device -> [connect ledger, unlock it with PIN, select Bitcoin app] -> Next -> [Select Ledger Device that is found] -> Legacy (don't touch the derivation path, it should be m/44'/0'/0' ) -> Choose to encrypt the wallet file or not That should recreate your Ledger Legacy wallet. If this finds nothing, then you need to go into the Electrum console and enter: [wallet.create_new_address(False) for i in range(100)]
Then enter: [wallet.create_new_address(True) for i in range(100)]
If it still finds nothing, and you see no transactions in the history tab, then the chances are very high that the 24 words you have written down are not the 24 words that your Ledger had before you wiped it. One last thing... did you ever use a passphrase (aka 25th word) with your Ledger?  |
|
|
|
Possibly you have connected to one of the "bad servers" that are trying to phish users into downloading fake versions of Electrum by sending fake error messages saying "you need to update to this version from <fake-electrum-website-link>" etc. The client was modified so that instead of showing the error messages verbatim, they only show specific errors. If they get an error that they don't recognise (ie. fake error from bad server), they give the "unknown error" message. If you go into the network settings (tools -> Network)... then right click on a random server in the list and select "use as server"... then try sending your transaction again. NOTE: You might need to try a couple before it works. Unfortunately, there are a lot of these "bad" servers |
|
|
|
I dunno, bitcoin.conf is empty by default so you might have set it unintentionally.
It seems they're sort of blindly copy-pasting stuff from "guides" that they've found... like they said they were following this: https://gist.github.com/bretton/1a72e9fea94405be449edbd379a1ce57Which is specifically "This guide is specific to getting LND and bitcoind running on ubuntu 16.04 LTS for testnet."  @crystal-love, are you actually trying to get a lightning node setup as well? or do you just want a Bitcoin Core node? |
|
|
|
Ok, in that case, Bitcoin Core and Armory are using the "default" locations for everything... that's very useful and means you don't need to worry about configuring any of the "pathing" stuff  Now you just need to wait for Bitcoin Core to fully sync up... once that happens then you should be able to run Armory without issue. |
|
|
|
stop breaking with recent wallets, handling will be done later though, thanks to HCP for handling that with his fork
I wouldn't say that my fork was "handling" recent wallets... it just ignores all the new data fields that were added so you don't get all the "NoneType" errors and the script doesn't error out when you run dumpwallet  I"m pretty sure the (very minor) changes I made will likely break other functionality of the wallet... but it means you can dump out one of the newer wallets without the script choking on (mostly) unimportant data |
|
|
|
It's just a plaintext file... it shouldn't require any sort of "fancy" editor like OpenOffice or Word or anything... Notepad or Notepad++ should work just fine. If it's full of garbage then something is broken somewhere |
|
|
|
To utilise .cookie auth... you just need to comment out or remove the rpcuser and rpcpassword lines from your bitcoin.conf file, then Bitcoin Core will automagically default to .cookie authentication |
|
|
|
Sorry to be a bore... but can you please post the dbLog.txt log file as well? There may be something a little more descriptive there: 2021-01-25 16:18:20 (ERROR) -- Traceback (most recent call last):
File "ui\TxFrames.pyc", line 948, in createTxAndBroadcast
File "ui\TxFrames.pyc", line 902, in validateInputsGetUSTX
File "armoryengine\Transaction.pyc", line 2513, in createFromTxOutSelection
File "armoryengine\Transaction.pyc", line 2414, in createFromPyTx
File "CppBlockUtils.pyc", line 3062, in getTxByHash
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x00000000047F8A80> >
2021-01-25 16:18:25 (INFO) -- TxFrames.pyc:827 - Change address behavior: NewAddr
2021-01-25 16:18:25 (ERROR) -- Traceback (most recent call last):
File "ui\TxFrames.pyc", line 948, in createTxAndBroadcast
File "ui\TxFrames.pyc", line 902, in validateInputsGetUSTX
File "armoryengine\Transaction.pyc", line 2513, in createFromTxOutSelection
File "armoryengine\Transaction.pyc", line 2414, in createFromPyTx
File "CppBlockUtils.pyc", line 3062, in getTxByHash
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x00000000047F8930> >
|
|
|
|
As mentioned in the issues... If you have the "fiat" value configured, it shows fiat on the "standard" preview window:  Nothing on the "Advanced" preview though. I guess the thinking is... if you're interested in "fiat" values, you would have "fiat" display turned on... and if you're using the "advanced" preview, you should really know what you're doing and be able to notice things like "excessive" fees... at least, I think you should if you're using the "Advanced" preview EDIT:It won't be difficult to do it, I'll see if I have the time in the future to do a pull request for this.
Sooooooooo, I got bored this morning https://github.com/spesmilo/electrum/pull/6968I'm hoping I did the whole pull request thing properly... I'm a bit out of practice with git and commits and pull requests etc! |
|
|
|
Thanks immensely guys. I really appreciate. But my query is this, how then do I get a hash I'd that shows the exact amount I sent?
My advice would be to click on the "BTC" button and leave it there... stop dealing in "USD" and trying to send "exact USD" amounts... it is an "impossible" task as the USD price of BTC is literally changing every second (depending on the source you use). If someone says "I want $10" and you're going to send them BTC, then you will need to agree on a set BTC-USD conversion rate (and/or a set price in BTC)... otherwise send them USD $10 via paypal or some other fiat currency transfer. It's the same with fiat transfers... if someone says "I want USD$10" and instead you send them EUR€8.22 and in the meantime the conversion rate goes to 0.83... you've only sent them "USD$9.90"... currency values flucuate... agree a price in whatever currency you are going to send, then send that amount. |
|
|
|
the closest I can think of would be the "received time" shown for a transaction on blockchain.com The time listed there is the timestamp of the block. Are you sure about that? The "tooltip" would suggest otherwise...  Check TransID: 0753895afa2c2f76b6a383a4ec2fe8efa87c583588dcb5fe7b9154dd50b57680Received Time: 2021-01-24 18:06Block was: 667422 BlockTime was: 2021-01-24 18:56Note: it's possible that for some transactions, blockchain.com might only see the transaction for the first time when it is included in a block... so you might get received time == block time... or it might be that the transaction was received a few seconds before the block was mined etc (as the timestamp is only to the nearest minute). |
|
|
|
Then i've got this error:
unable to load RPC credentials for bitcoind: please set all or none of bitcoind.rpcuser, bitcoind.rpcpass, bitcoind.zmqpubrawblock, bitcoind.zmqpubrawtx
Not sure why you're using bitcoind.zmqpath? the options required are: bitcoind.zmqpubrawblock and bitcoind.zmqpubrawtx as per the error message you are seeing. What is the contents of your bitcoin.conf file in the the /home/user/.bitcoin directory? Then i removed command "rpcuser and rpcpass" and got this:
Attempting automatic RPC configuration to bitcoind
unable to load RPC credentials for bitcoind: unable to extract RPC credentials: unable to find zmqpubrawblock in config, cannot start w/o RPC connection
As for rpcuser and rpcpass, if you pass the bitcoind.dir to lnd, it should automatically find the .cookie file and use those credentials |
|
|
|
Master key matches the key I have on the providers website. but where it says "Next 5 addreses generated by your public key"
None of those addresses match my wallet.
In which case... it's most likely that the provider is not using the same derivation path as Electrum... For instance... from this xpub from Electrum: xpub661MyMwAqRbcFFuDRX7BMSzUcPukXGRQE7Wqmy2YiekQS56meYFDke48usmCpiYo6ZGkNjRQKnMSMnXrsPaezthU3uyWwj27CxxTs8NYgqF  Electrum uses the derivation path: m/0/x to generate the addresses... so the first address I see in Electrum is: 1JmZPy7YG4TRMovrSpN4RLAGcGYuhcAbso  You can confirm on: https://iancoleman.io/bip39/ Put the xpub into the "BIP32 Root Key"... click BIP32 Tab... set "client" to Custom, set BIP32 derivation path to: m/0  You will then see the address at the bottom:  Does the service provider give any hints on what the derivation path they are using for xpub's is? If not, you might need to experiment with your xpub and the iancoleman BIP39 tool above to figure it out. Are you able to advise which provider you're using? |
|
|
|
Or is there an online service that has this information available?
I'm not sure if Electrum stores the time it was broadcast... the closest I can think of would be the "received time" shown for a transaction on blockchain.com:  But that is only indicative of the time that the transaction was (last) received by blockchain.com... it may have been dropped/rebroadcast etc... Bitcoin core seems to store the time it first saw the transaction... but if the node isn't running, that "received time" may not be when it was first broadcast etc. Why is the "broadcast" time important to you? What are you attempting to determine exactly? |
|
|
|
But true, reminder for everyone else, need all xpubs and not just the minimum number of signatures. Whoever makes the watch-only wallet should duplicate all of those xpubs for everyone else (or have multiple backups).
Everyone will need everyone else's Master Public Key ("xpub") anyway... as everyone participating as a co-signer will need to have their own "copy" of the MultiSig wallet to be able to sign transactions... you can't import partially signed transactions from the multisig and sign it from your "standard" wallet, even if you used the master public key from that "standard" wallet to create the multisig. You'll get "Transaction unrelated to your wallet":  So, effectively everyone participating should have: - Their own seed/Master Private Key and xpub - xpub's from all other parties involved |
|
|
|
Based on the answers you guys provided, am I correct that
- The private keys allow user to extract information (like how many currently owned) from the blockchain and they do not change when when transactions occurred.
You can technically do this with just public keys as well (that's how you create a "watching-only" wallet... it has the ability to "look" at the blockchain and find all the transaction history for the public keys that it holds.) Public keys are derived from Private keys... but it's a one-way process... private key ---> public key... so if all you have is public keys, you can "look" but not "touch" - When an transaction happened, the information is saved in the blockchain.
Correct... all information for all transactions is stored on the blockchain. - Ledger Live is just an interface which user can use to see the coin information extracted from the private keys from the blockchains and to be able to manage the coins.
Effectively yes... all "wallet" applications are just interfaces for managing private keys, viewing transaction history and signing/broadcasting transactions. - As long as I have the seed to the private keys, these private keys (and therefore my coins) will not be changed when a specific app is removed.
Sort of correct... Your Ledger holds the seed within it's secure element... from this seed, each coin app is able to to ask the secure element to derive it's particular set of private/public keys at will... if you remove a coin app on the device, nothing changes because the your seed is still stored in the secure element... and the transaction data is all contained on the blockchain... and you can't delete that! If you re-add the coin app... it's able to ask the secure element to derive exactly the same set of private/public keys... this is why the system is referred to as a " deterministic wallet"... as long as you have the same "seed" (which you can restore from your 24 words if required), you will always be able to generate the same set of private/public keys. So, if you get another Ledger device (or any other BIP39 device or wallet application) and put the same 24 words in... it will regenerate the same seed... and therefore the same set of private/public keys. This is the main reason why safely and securely backing up your 24 words is sooooooooo important! Those 24 words effectively allow full access to ALL your funds. |
|
|
|
The key you see under your bitcoin address and in front of PrivBase58 is your private key.  NOTE: it pays to tick the "Omit Spaces in Key Data" box at the bottom of this window... pretty much ALL wallets will refuse to accept private keys with spaces in them like they default to in this export screen in Armory.  |
|
|
|
Got it. Just did that and got the private keys. Thinking about the next steps to encash that in to USD.
Once you have the private keys imported into a wallet like Electrum, you'll either need to sign up at an exchange that supports outputting to your bank/paypal etc... or find a buyer and do a "P2P" (Peer to Peer) transaction. The former will no doubt involve "KYC" (know your customer) requirements and involve handing over your personal details (name, PhotoID, address, phone, social security, passport blah blah blah)... While the latter holds more "risk" of being ripped off by a scammer that fails to pay, uses a reversible payment method (PayPal etc), or a fraudulent payment method (hacked account/stolen credit card etc). Best of luck. |
|
|
|
|
Show Posts
