Their site says that it needs to be at least 0.0001BTC/kb which is around 10000 satoshi (If I remember rightly).
Yeah you're right here, at least 10k satoshi for the fee Fee per byte which is sat/byte doesn't involve about it, the important is the total fee of the transaction which is he have just 0.0000565 BTC or around 5k sat. No, you're wrong. You're reading the requirement incorrectly... it is NOT based on total fee... fees are ALWAYS (and should always be) calculated using fee per byte. This is why the fee estimators ALWAYS use BTC/kB or sat/byte because that is the value that miners use to prioritise transactions. It says on ViaBTC: We only provide accelerator services for those with at least 0.0001BTC/KB transaction fees;
That is 0.0001 BTC per kiloByte or 10,000 sats per kiloByte or 10 satoshis per byte... His transaction was 25 sats/byte and as far as I could tell, met ALL the requirements of ViaBTC. |
|
|
|
Firstly, Bitcoins don't go "missing"  But you're going to have to give us some more information to be able to help. You say that you are moving your bitcoins to Electrum, but what wallet were you sending your bitcoins FROM? Can you provide a Transaction ID (TXID) of the transaction that you created so we can see if it is just a case of an incorrect fee? It's possible that by getting mBTC and BTC confused, you've attempted to send a REALLY tiny amount of bitcoin... possibly with a really tiny fee... and the transaction is just unconfirmed. |
|
|
|
If you are the "owner" of that Bitcoin address, then you should be able to "spend" those unspent transaction outputs (UTXOs) by opening your bitcoin wallet, selecting "Send" and create a transaction that sends a given amount of bitcoins to another address. The wallet will automagically select the appropriate UTXOs that are contained in your wallet to include in the transaction that you create. Given that the address you have provided the link for is a "Multi-Signature" address, (ie. it starts with a "3")... then at least one other party is going to need to provide authorisation to any transaction that you create. Which wallet software are you actually using? Did you create a "Two Factor Authentication" wallet of some description? |
|
|
|
You can see the "technical specs" of the passphrase in BIP39: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawikiSpecifcally: To create a binary seed from the mnemonic, we use the PBKDF2 function with a mnemonic sentence (in UTF-8 NFKD) used as the password and the string "mnemonic" + passphrase (again in UTF-8 NFKD) used as the salt. The iteration count is set to 2048 and HMAC-SHA512 is used as the pseudo-random function. The length of the derived key is 512 bits (= 64 bytes).
So any passphrase you choose, gets concatenated with "mnemonic" and is used as a salt. ie. if your passphrase was "Th1sI5mYp@ssphr@se"... it would be "mnemonicTh1sI5mYp@ssphr@se" being used as the salt and an iteration count of 2048. Also, as mentioned in the BIP, ANY passphrase provided will generate a valid seed... so an attacker would then need to check addresses for every generated/tested passphrase for coins further slowing down any attack. As long as your passphrase isn't "abc123" and/or the attackers aren't using huge computing clusters then even if your mnemonic gets compromised, you should have plenty of time to move your coins. |
|
|
|
They have one thing right - use another wallet, MultiBitHD is faulty rubbish - useless as a mission-critical program. Avoid it.
Pretty much... There is also the dreaded " Password did not unlock the wallet" issue which they don't seem to have fixed yet either. I honestly have no idea what the KeepKey guys are doing... but these issues have been known about for months now and there doesn't seem to have been any hint of any update for MultiBit HD. The last commit to their github was on March 8th!!?!  |
|
|
|
Who did you create the MultiSig address with? What was the m-of-n setup for this MultiSig? Was it 2-of-2, 2-of-3 or something else? When you created the MultiSig, which option did you select here:  Also, have you enabled the "cosigners pool" plugin? "Tools -> Plugins":  |
|
|
|
Im using electrum 2.7.8 You should update your Electrum BTW... It is quite a few versions behind the latest version of 2.8.3. There were some bugs in the "older" versions of Electrum relating to Dynamic Fees. Where even with Dynamic Fees checked, it may not actually be calculating dynamic fees properly. Having said that, currently the network load is pretty small compared to a month or so ago when there was 150,000+ unconfirmed transactions. Now, it seems to be less than 5,000. So the fees required a no longer massive. My suggestion is to keep an eye on 1, 2 & 3: 1. https://blockchain.info/charts/mempool-count2. https://btc.com/stats/unconfirmed-tx3. https://bitcoinfees.21.coIf the mempool starts getting full of unconfirmed transactions (>10K unconfirmed), you'll probably find that the recommended fees start climbing again... and you may find you need to move the slider more to the right to get your transactions confirmed. But at the moment, as it isn't busy, having the slider all the way on the left *should* be fine. Finally, as a safeguard, you can always check the "replaceable" box so that you can use "Replace-By-Fee" functionality built in to Electrum (not sure if that was in version 2.7?) and "Bump Fee" for your transactions if they get stuck. |
|
|
|
Is the software of Trezor open source ? I know it was but they changed something many people were unhappy, how about now  I believe you can find all the TREZOR stuff on github here: https://github.com/trezorIt seems to have all the APIs and Libraries for implementing TREZOR support into your applications, as well as the sources for firmware and even schematics for the hardware. How about ledger, is it open source ?  Ledger have a github here: https://github.com/LedgerHQ |
|
|
|
i need a script like this:
array like this...
chances = {11,12,13}
bets = {1000,2000,3000}
increase = {1.16,1.17,1.18}
but change random when profit is 0.1 btc
It isn't very clear what you actually want your script to do. Do you mean that you want it to randomly select a chance, bet and multiplier from your Array when your profit is > 0.1BTC? What should it do when profit is < 0.1 BTC? hello guys, please i need help adding a command to the following script, that will make the bot reset seed if i get 3 losses in a row chance = 49.95
base = 0.00000001
count = 0
tot = 1
tot2 = 1
abc = 0
cba = 0
nextbet = base
function dobet()
if profit>0.000000001 then
count = 0
tot = 1
tot2 = 1
abc = 0
cba = 0
base = 0.00000001
resetstats()
end
if base == base then
tot = 1
tot2 = 1
end
if base == base*2 then
tot = 2
tot2 = 1
end
if base == base*4 then
tot = 4
tot2 = 1
end
if base == base*8 then
tot = 8
tot2 = 1
end
if base == base*16 then
tot = 16
tot2 = 1
end
if base == base*32 then
tot = 32
tot2 = 1
end
if base == base*64 then
tot = 64
tot2 = 1
end
if base == base*128 then
tot = 128
tot2 = 1
end
if base<0.00000001 then
base = 0.00000001
count = 0
abc = 0
cba = 0
end
count = count+1
if count>10 and abc>cba then
base = base/2
count = 0
abc = 0
cba = 0
end
if count>10 and abc<cba then
base = base*2
count = 0
abc = 0
cba = 0
end
if win then
abc = abc+tot
nextbet = base
else
cba = cba+tot2
nextbet = base
end
end
end
end
thanks Firstly, as previously mentioned, that script is broken... all those "if base == base*2", "if base == base*4" etc... will NEVER return true... they need to be fixed for your script to do anything. To reset the seed, check the "currentstreak" inbuilt variable in the "loss" section of your script (it's the "else" section of your "if win then")... currentstreak shows the number of wins or losses in the current streak. Win streaks are are positive number, loss streak are negative number ie. currentstreak == 10 is a 10 win streak currentstreak == -5 is a 5 loss streak ...
function dobet()
...
if win then
abc = abc+tot
nextbet = base
else
cba = cba+tot2
nextbet = base
if currentstreak == -3 then
resetseed()
end
end
...
end
|
|
|
|
Wallet.dat files only work with Bitcoin Core. As far as I know, no other wallet application works with this file format. There is also the pywallet script that supposedly works with wallet.dat files, but I've found that it is a little outdated and doesn't play nicely with newer versions of wallet.dat files from newer versions of Bitcoin Core. As HITEC suggested, I'd make a few backup copies of what you have recovered... then, grab a copy of Bitcoin Core... depending on how old your copy of Core was... you can find all the history releases here: https://bitcoin.org/bin/I'd probably start with 0.14.x and work backwards until you find a version that works with the wallet.dat you have. I think the newer versions will read and "upgrade" older versions, (hence why you might want to make multiple backup copies) but I'm not 100% on that. Otherwise, check out Pywallet ( https://bitcointalk.org/index.php?topic=34028.0) and see if that works with the wallet.dat |
|
|
|
I've written some python scripts that were meant for MultiBit HD that also creates bitcoinj wallets in protobuf format... It didn't extract the keys and just dumped out the raw protobuf. What was interesting to note was that the 12 word HD seed is actually available in plaintext in the dumped out data! So, I fired up gurnec's: decrypt_bitcoinj_seed and sure enough, it output the recovery seed! You can then put the recovery seed into an offline copy of: https://iancoleman.github.io/bip39/There are instructions at the bottom of the page for downloading etc Put the seed into the "BIP39 Mnemonic" section at the top. Then click "BIP32" under Derivation Path, set "Client" to "Custom Derivation Path" and set the "BIP32 Derivation Path" to: m/0'/0  All your addresses/keys will be displayed at the bottom.  NOTE: You may need to click "show more" to see all your addresses if you have used more than 20 receive addresses... and you'll also need to set the "BIP32 Derivation Path" to: m/0'/1 to get access to your change addresses!  |
|
|
|
With Bitcoin, you technically don't directly specify the fee as such... You specify the inputs and outputs and the fee is just the difference between total inputs and total outputs. That is to say: Transaction Fee = Total Inputs - Total Outputs. createrawtransaction [{"txid":"id","vout":n},...] {"address":amount,"data":"hex",...} ( locktime )
Create a transaction spending the given inputs and creating new outputs.
Outputs can be addresses or data.
Returns hex-encoded raw transaction.
Note that the transaction's inputs are not signed, and
it is not stored in the wallet or transmitted to the network.
Arguments:
1. "inputs" (array, required) A json array of json objects
[
{
"txid":"id", (string, required) The transaction id
"vout":n, (numeric, required) The output number
"sequence":n (numeric, optional) The sequence number
}
,...
]
2. "outputs" (object, required) a json object with outputs
{
"address": x.xxx, (numeric or string, required) The key is the bitcoin address, the numeric value (can be string) is the BTC amount
"data": "hex" (string, required) The key is "data", the value is hex encoded data
,...
}
3. locktime (numeric, optional, default=0) Raw locktime. Non-0 value also locktime-activates inputs
Result:
"transaction" (string) hex string of the transaction
Most wallets calculate the fee (or let the user specify the fee) and then just adjust the "change" output such that the difference between inputs and outputs equals the calculated fee. NOTE: this may mean adding additional inputs to cover the fee and/or making the change = 0 and not having a "change" output. Not sure how this works with the Omni Core Fork tho... given that it is a fork of Bitcoin Core, I would assume it works the same way... |
|
|
|
Just to throw a little spanner in the works... how about Blockcypher's API? https://www.blockcypher.com/dev/The "free" limits are relatively low... but enough to have a decent play with the system to get used to it. They have examples for cURL, JavaScript, Ruby, Python, Go and PHP At the end of the day, it is probably mostly about personal preference as to which one you want to use. If you get serious, then speed and cost are probably going to be a deciding factor. |
|
|
|
He means "air gapped"... basically, it is as described above... a computer disconnected from all networks (and other devices). The idea being that it helps to prevent any hacking or malware etc unless the person has physical access to the machine. The "Live" distro is a self contained Operating System that will boot from a dvd/cdrom or usb drive and does not require any permanent storage. It will load itself completely into RAM without needing any harddrive etc. "Tails" is one of the more widely known "live" distro for the crypto world: https://tails.boum.org/ |
|
|
|
The token file is just a text file... use any text editor you like... and follow the instructions to create the various tokens in the file. You put it in the same directory that you run btcrecover from. This file, typically named tokens.txt, can be created in any basic text editor, such as Notepad on Windows or TextEdit on OS X, and should probably be saved into the same folder as the btcrecover.py script (just to keep things simple). Note that if your password contains any non-ASCII (non-English) characters, you should read the section on Unicode Support before continuing. As for running the process: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#running-btcrecoverDid you read any of the tutorial or instructions on the btcrecover github?? |
|
|
|
That code has to be typed on 2 lines... so type: and then press enter, you should then see "..." appear.  Then type a couple of spaces (I usually use 2, but whatever you like) and the next line of code: print wallet.create_new_address(False)  and then press enter a couple of times and it should generate your new addresses... NOTE: You'll also want to do the same thing and use "True": for x in range(0,50):
print wallet.create_new_address(True) to generate some new change addresses in case your coins were in a change address. NOTE: you may need to close and re-open your wallet to get the new addresses to show |
|
|
|
Since Uquid uses bitpay's invoice system, the transaction expires within 15 minutes if there is no (single) confirmation for the transaction with the amount mentioned in the invoice. That is incorrect. Bitpay invoices do not expire within 15 minutes if there is no confirmation. You have 15 minutes to broadcast the transaction on the network before the invoice expires. I have purchased several items from several different merchants (eGifter, Steam etc) who all use Bitpay as their payment processor. As long as you broadcast the transaction (and make sure the amount you send is correct) within the 15 minutes, Bitpay detects the "unconfirmed transaction" and just marks it as pending. They were even nice enough to give me warnings that my fee was too low and the transaction make take a while to complete. Later, in some cases several hours later, when my transactions finally got a confirmation, it was marked as such by Bitpay... and the merchants processed my orders. Given that the block time is an "average" of 10 minutes... there are instances where the time between blocks has been over 15 minutes... how are you supposed to get a confirmation (even assuming you pay the best fee and get included in the next block) if there are no blocks mined in the 15 minute window that Bitpay provide? Bitpay understand this and that is why it isn't based on confirmations. You just need to send the transaction. Check out the block times from the last 10 blocks:  |
|
|
|
You can always see if there are any "whales" in your area on localbitcoins.For sums that large, any face to face meetings should probably be conducted in a very public (and safe) location... like a police station (assuming your local police aren't corrupt  ). If face to face isn't an option, then you'll seriously want to consider using an escrow service... honestly for sums that large, 1% fee (~$200) for the security of not getting screwed is chump change... and you'd probably be able to negotiate a fixed rate anyway. |
|
|
|
Pretty much the options are: a. find the keypair.txt that your friend didn't download. b. contact PeerPlays support and see if they can assist. It would appear that they have already tried a. I’ve checked my hard drive, the recovered deleted files, etc. It’s not anywhere. I cannot tell if they have tried b. This is a little confusing: I would like to ask you if you can help me to recover my 3570 PPY lost. I know that there are rules in the code, but maybe we can find a way to prove that the donor address it’s mine. I may sign a message or provide the private key from 15r8TL98kj4KZpK4xy77MikpZLMHiFh33D Or if you can give me any other suggestion. Any ideas?
This amount of money means a lot for me, I’m almost not sleeping during the last week and I’m desperate. Please help me to get the tokens that I really owe but I can’t claim.
Did they send this message to you or PeerPlays support? Hopefully the PPY Support can assist... otherwise, it is another case of someone losing a substantial amount of wealth through ICO's and their stupid "claim" systems... It should be easy enough for the PPY people to look at the blockchain and see a 10BTC transaction from an address (I think you've listed the incorrect one btw... the 10BTC being sent from 15r8TL98kj4KZpK4xy77MikpZLMHiFh33D is this transaction: https://blockchain.info/tx/712c03a4c3148d1f1ffa7f76a366271cd5c00fccc8758466e08230ae394b80b9PPY should be able to determine that 1B9By9C9inLujsB3s1TJ2CSG2AGA43HEzR is their address, currently containing 10BTC Your friend should be able to sign a message from their address (15r8TL98kj4KZpK4xy77MikpZLMHiFh33D) to prove ownership. That is why these functions exist... this whole convoluted system PPY has set up seems to be aimed at making it difficult for folks to claim their tokens and effectively lose their money. Especially changing the rules halfway through... |
|
|
|
|
Show Posts
