Latest posts of: HCP

Quote from: witke on June 04, 2017, 07:10:45 AM

trying to broadcast offline signed transaction, but got this error "The transaction was rejected by network rules. (16: mandatory-script-verify-flag-failed (Script failed an OP_WQUALVERIFY operation))". Electrum 2.8.3

Did you copy and paste that error? or type it in manually... because it should be OP_EQUALVERIFY.... not OP_WQUALVERIFY Huh

If it was copy/paste... Did you accidentally modify one of the transaction files while you were moving things around?

Quote from: European Central Bank on June 04, 2017, 01:39:17 PM

there seem to be 5-10 threads a day on r/bitcoin complaining about tiny fees with electrum. maybe it's giving them too much choice.

And then you ask what version they're on and you get "2.5.x"... Roll Eyes

Run the latest version (currently 2.8.3)... Tools -> Preferences -> Fees... turn "Dynamic Fees" on... set "Replace By Fee" to "Always"... Then use the slider on the "Send" tab to 'fine tune' the fee as you desire...

If the whole BTC/kB thing is a bit confusing... tick the "Edit Fees Manually" box and a text box appears next to the slider showing the exact fee that has been calculated. PROTIP: DON'T actually manually edit the fee tho! Tongue

Quote from: xIIImaL on June 04, 2017, 02:06:08 PM

... or Multibit wallet...

Don't go anywhere near MultiBit HD at the moment... there is a pretty serious error that has been hitting users lately... some folks are getting a "Password did not unlock the wallet" error when starting up, even though the password is 100% correct...

It's been a known issue for at least 2 to 3 weeks now... no sign of an update as yet... Devs don't seem terribly active...

This is locking people out of their wallets, and because MultiBit uses a somewhat 'unique' BIP32 Derivation Path (m/0'/0), there aren't a lot of choices for alternative wallets that are compatible with MultiBit seeds... the only 2 wallets that are currently know to be compatible are "Breadwallet" (on iOS/Android) and "Simple Bitcoin Wallet (Android)...

Quote from: sree6020 on June 04, 2017, 12:51:12 PM

Is there a way to choose the magicNum randomly between a set range.

Anyway THANKS FOR HELPING ME with the code .

Apparently "math.random(lower, upper)" generates 'random' integer in the range between 'lower' and 'upper' INCLUSIVE

so something like:

math.randomseed( os.time() )
magicNum = math.random(10,15)

should randomly generate a number from (10,11,12,13,14,15)

... you're welcome

Quote from: Autoband86 on June 04, 2017, 09:37:54 AM

Does anyone know how the wallet.cipher files are encoded? Or how the encryption of the bitcoin wallet can be split to see which parts are encoded/where the IV and Salt are?

So as I PM'd you... I went ahead and read through the multibit code to figure out the file format for the wallet.cipher files... and how they are meant to be decrypted... Then attempted to recreate that Java code in Python... I did a quick test and it seemed to decrypt my wallet.cipher (using my wallet password) and spat out an unencrypted wallet file containing unecrypted keys... and displayed my addresses and private keys... so I *think* it works...

#fingersCrossed

For anyone who wants to try it or is curious, the "ugly code" is currently here: https://pastebin.com/2PYVG6My

Once it is confirmed that it is working "properly" and with some more testing, I'll tidy up the code and add it to the github project

Quote from: sree6020 on June 03, 2017, 06:27:19 PM

Can you please help .I want to write a program performing the following functions in dicebot.

There is an initial bet.After 'N' number of bets the bet amount must be equal to balance.And the nextbet reverses to initial bet .And again after N bets the bet gets equal to balance.and so on.....

for example: Suppose I have a base bet =0.00000001. Let N=13.Then the 14th bet is equal to balance.And the 15th bet is again 0.00000001.And again after 13 bets the process continues.

That seems pretty easy...

Code:

basebet = 0.00000001
magicNum = 13
count = 0
nextbet = basebet

chance = ????? -- You need to set this!
bethigh = true -- or false depending if you want high or low

function dobet()

  count = count + 1

  if count == magicNum then
    -- Time for MAX bet
    nextbet = balance
  elseif count > magicNum then
    -- Time to reset
    nextbet = basebet
    count = 0
  end

end

It also seems like an easy way to lose all your balance... buy hey... your coins Tongue

Quote from: sree6020 on June 03, 2017, 06:27:19 PM

Can you please help .I want to write a program performing the following functions in dicebot.

Try the programmer mode discussion thread... Wink

It may not have been scammed. What I was asking was whether you had sent the coins to an account on an online service.

Generally speaking, a lot of these services use a system whereby you don't have access to a specific address/key pair. They say "your deposit address is XYZ"... This doesnt mean the address is yours, or stores your coin. any money you deposit is then simply credited to your account balance (effectively a number in a database, no longer linked to your initial deposit). When it comes time to settle your account (aka you want to withdraw some or all of your available balance), they simply send the required amount from any address they own (ie. could be someone elses deposit) and adjust your balance to reflect this.

So while the coins you deposited may have been used to settle other users withdrawl requests, theoretically they can use other peoples deposits to settle the requests. (assuming the site isnt a scam and the owners arent stealing coins)

If you deposited 10 BTC, your account should reflect that fact... if it doesn't then it is either due to the change to this paymium thing and is a mistake, or you could have been scammed.

85 characters is a bit odd...

Could be a 34 char public address + 51 char private key in WIF format or a 33 char pub address + 52 char compressed private key in WIF format.

Is there a 5 at char 35? or an L or K at position 34??

Honestly, given all the issues people are having with MultiBit HD lately... my first piece of advice is get all your coins out of MBHD and into a different wallet...

As far as backing up your wallet... you only need the 12 (or 18 or 24) "seed" or "wallet words" that you should have written down when you created the wallet... If you have those words, you can recreate your entire wallet at any time (assuming MBHD is working properly Tongue

)

There would also have been a 6 digit "datestamp" in the form "1234/56"... it isn't strictly required, but it helps speed up the resync should you need to restore your wallet, as it lets the app know which date your wallet was created and to ignore the blocks generated before that date.

If you still want to backup your wallet file... In finder... "Go" -> "Go to folder":

Type in "/Users/YOURUSERNAME/Library"... for instance, if your username is Simon:

Look for the "Application Support" folder:

Then the "MultiBit HD" folder:

Then look for folders that start with "mbhd-" (NOTE: if you have multiple wallets, there will be multiple "mbhd-" folders):

Inside each of these you will find a "mbhd.wallet.aes" file... this is your wallet file... back that up however you like:

You could also just backup the WHOLE "mbhd-" directory(s) I guess... As mentioned though... NONE of this is necessary as long as your have your seed words. Wink

At this point, your only options are to either use the pay service at viabtc.com... (or the pushtx.btc.com)

or if you own the address (1Mfvne1x62nAiZtBEbrwBQsvtyiCssM346) that got the dust output of 0.000009 BTC, you can try and use that particular UTXO to execute a "Child Pays For Parent" transaction and use BIG fee so the average fee for both your transactions ends up being at or over the recommended fees (currently ~350 sats/byte)

Given your first transaction was 2440 bytes... and the next transaction will need at least 2 inputs your total combined size is going to end up being at least 2780 bytes. Your total fee for this would need to be 2780 * 350 = 973000 sats = 0.00973000 BTC, you've already paid 0.00090080... which brings it down to "only" 882920 sats or 0.00882920 as a MINIMUM.

You may as well just pay ViaBTC the 0.01 BTC and let them deal with it Tongue

Ahhhhh that explains it... Electrum is protecting you from yourself Wink

It is preventing your transaction from generating a dust output... having a UTXO of 43 sats sent back to your wallet is just completely pointless... as an input to a new transaction, it would require 148 bytes, at even stupid low fee of 1 sat/byte, you'd need to pay 148 sats, to use that 43 sat UTXO as an input to a transaction.

Now do the math with current fee rates of 300+... all of a sudden, your 43 sat UTXO is going to cost 44,400+ sats to put in a transaction...

be thankful Electrum wants to give it to the miners... it's cheaper Tongue

It is also possible that whatever service you used to buy BTC is using a different data source for it's BTC to $ conversion than your wallet, which would explain some discrepancy... not sure it is likely to be responsible for 50% tho... Tongue

I would think that Abdussamad is likely close to the mark... the service you used probably has horrific exchange rates and fees... what service did you use? and are their rates and fees listed clearly?

Quote from: digaran on June 01, 2017, 07:19:21 AM

Destroying this business and promote my own is my job as it is the rule of the market/business.

Quote from: digaran on June 01, 2017, 01:13:26 PM

In business you don't go cuddle and give a BJ to the competition, you go for the weak points and crush them out of their jobs.
Survival of the fittest bitches, if you are not ready for such an environment then you'll get crushed and killed. bitches right? lol

Quote from: digaran on June 03, 2017, 10:37:53 AM

...I have no intention to accuse/attack any body here, I'm not calling any body a scammer here, all I said was that I have the incentive to be here and discuss with reason, if you want to see it as an attack then so be it....

Really? Seems like you missed your calling as a politician... with such a short memory and natural talent for back tracking... Roll Eyes

If you wanted to "discuss with reason"... maybe spend a little less time on chest-beating and juvenile 'size' tags... and a bit more time putting some thought into your criticism and/or "reasoned" debate...

I wonder if it might be some weird little rounding error somewhere when calculating the payment, change and fee sizes? 9 satoshi's seems like a really odd amount for it to be "out" by... Huh

As far as I can tell... the only 'advantage' Jaxx has is that it is "multicoin" and has "shapeshift" support built in... and some might say that "it looks pretty". However, if you're not interested in alts or converting your coins, and you prefer function over form, then Jaxx effectively has no advantage.

For storing BTC longterm, I'd have to recommend cold storage using an offline Electrum wallet (air gapped computer or USB stick Linux distro with Electrum installed)... or a secure paper wallet.

Quote from: Zegra on June 03, 2017, 12:35:43 AM

Yes, the problem was indeed that my coins get moved when the public key changes. Which means I would have to keep register my new public address with the Byteball bot and sign a message, which is a time consuming task. TryNinja's solution was fine.

Just realise that the private key/address you have generated is NOT included in the 12 word seed you got when you created your Mycelium wallet. As such, it is NOT recoverable with the seed words should you lose your phone.

Make sure you have secure backups of that private key, write it down offline somewhere safe... if you don't and your phone is lost/stolen/broken... any coins in that address (which I'm going to assume is most/all of your coins on June 9th) will be lost forever. Undecided

Can you take a screenshot of your %appdata%\MultiBit directory?

You are looking for a "[walletname]-data" directory. My wallet is just called multibit.wallet, so I have a "multibit-data" directory...

And then in that, there should be some "-backup" directories...

hopefully the key-backup and/or wallet-backup and/or rolling-backup directories have some files in them. The "wallet-backup" one might be a good place to start... but failing that, the "key-backup" directory might have files that contain your private keys!

These files can be generated automatically by MultiBit, so even if you haven't explicitly backed up the wallet file or exported your keys, there is a good chance the files still exist!

Right... so you want a guaranteed 10% return per day with no risk? Roll Eyes

That just isn't going to happen. With a bankroll of 0.01BTC, at 2x payout (~49.x chance) and 1 satoshi basebet, you can only survive maybe 18 losses... as crazy as it sounds, losses of 20+ aren't unheard of at that chance of winning.

Have you looked for any of the scripts that have been promoted around this subforum? or on Seuntjie's site?

Quote from: Phyzyprogrammer on June 02, 2017, 06:37:47 PM

i mean a script that can withstand a long lossing treck even with 0.01btc deposit

Ohhhh you meant a "safe" script... no such thing... it's called gambling for a reason. Tongue

There are plenty of example scripts floating around these forums and even some on bot.seuntjie.com site...

But if you want a truly safe script:

Code:

nextbet = 0
chance = 100
function dobet()
  stop()
end

Guaranteed not to lose! Wink