I have a script which creates many addresses in one wallet and can mix my coins between them. It's the safest way, 'cause coins always with you and you know that nobody have mix logs. If you're programmer you can write such script for yourself. It's not hard
All you are doing is paying fees to move your coins around addresses inside your wallet. You are not "mixing" anything. As soon as you attempt to create a transaction that requires more coins than you have in one address, your wallet is going to add in extra input(s) and then those addresses are forever linked as being controlled by the same person/entity. Additionally, it is highly likely that funding of your multiple addresses all comes from common parent addresses/transactions... which would probably enable someone to link all those addresses without you spending the coins. A true mixer will enable you to have multiple addresses that are in no way linked to one another... and obscure the source of those coins. |
|
|
|
I have made a try with your code and it seems to work bcos there is no "Too long header" error. But when I place a buy order it said: TypeError: Cannot read property "0.01" from undefined. (line 77). (Line 77: return dataAll[parameter][subparam] }; They said the Rate is not defined.
That error is just because it is attempting to parse the return JSON from Poloniex incorrectly... if (parameter === undefined) {
Logger.log(JSON.stringify(dataAll))
return JSON.stringify(dataAll) }
else if(parameter != undefined && subparam === undefined) {
return dataAll[parameter] }
else if (parameter != undefined && subparam != undefined) {
return dataAll[parameter][subparam] }
}
This code is assuming that the "parameter" and/or "subparam" that you pass into the poloniex() function is one of the keys that comes back in the JSON return string from Poloniex... however, the example output that the API docs give for a "buy" command is: {"orderNumber":31226040,"resultingTrades":[{"amount":"338.8732","date":"2014-10-18 23:03:21","rate":"0.00000173","total":"0.00058625","tradeID":"16164","type":"buy"}]} So the "keys" are "orderNumber" and "resultingTrades"... resultingTrades has subkeys of "amount","date","rate","total","tradeID" and "type". What has likely happened is that your BUY order has probably been placed, but your script just failed to read the result from Poloniex... as it was trying to find a key called ["BTC_ZEC"] with subkey ["0.01"] which won't exist. Check your poloniex order history and see if it got placed. To fix the error, you'd need to put in some code that returns something that SHOULD be returned by a successful API "buy" call... Also, you should probably put some error checking in that checks to see if the API response was an error code: if (dataAll["error"] != undefined) {
//oh oh, something went wrong!
Logger.log("Error: " + dataAll["error"]);
return dataAll["error"];
}
if (parameter === undefined) {
Logger.log(JSON.stringify(dataAll));
return JSON.stringify(dataAll);
} else if (command === "buy") {
return dataAll["orderNumber"];
} else if(parameter != undefined && subparam === undefined) {
return dataAll[parameter];
} else if (parameter != undefined && subparam != undefined) {
return dataAll[parameter][subparam];
}
I'm not sure what data from the response you actually want to display, so I just picked the "orderNumber"... And I did not see you add more one params in the poloniex function (still has 3 params but we are sending 4?)
Instead of using the "named" parameters (command,parameter,subparam) listed in the function definition... I just used arguments[0], arguments[1], arguments[2], arguments[3]... and check that the "command" is "buy", so therefore there should be 4 "arguments" (0,1,2 and 3) passed in to the function. |
|
|
|
I have the same thing pop up but right after installing I haven't made a wallet on electrum that is the first screen when I first opened program I deleted everything and tried again am I missing something please help thanks
But that is what it is supposed to do after installing... you need to create a wallet. If you're saying it is actually asking for a password, then it would appear you've already used Electrum before and there is already a "default wallet". Electrum stores the user data and wallets in %appdata%\Electrum (on Windows this is usually something like C:\Users\YOURUSERNAME\AppData\Roaming\Electrum) NOTE: If you can't find the AppData directory, it'll be because it is hidden by default. Instructions for showing hidden files/folders: https://support.microsoft.com/en-us/help/14201/windows-show-hidden-filesI suggest that you backup the "wallets" folder (just in case you actually have some BTC in there already)... then just delete the entire %AppData%\Electrum folder and then start Electrum. It should recreate the folders and start the "first run" wizard that lets you create a new wallet. |
|
|
|
I've had a quick play with Google App Script, to be honest, I'm not terribly familiar with it... but it seems to be Javascript based. A couple of things I've found wrong with your script... for (i = 0; i < signature.length; i++) {
var byte = signature;
if (byte < 0)
byte += 256;
var byteStr = byte.toString(16);
if (byteStr.length == 1) byteStr = '0'+byteStr;
stringSignature += byteStr;
}
This code isn't getting each character of the signature and converting to a hex string, as seems to be the intent... instead it is getting the ENTIRE signature array each time through the loop... so, I was getting "Header too long" errors... You need to change the 2nd line in the loop to: var byte = signature[i];
So that it gets each character one at a time. Secondly, as I expected, it isn't setting the parameters... so the payload ends up being "nonce=bigLongNumber&command=buy"... but it doesn't include the currencyPair, rate or amount. So instead of this: var payload = {
"nonce": nonce,
"command": command
}
Try something like this: if (command === "buy") {
var payload = {
"nonce": nonce,
"command": arguments[0],
"currencyPair": arguments[1],
"rate": arguments[2],
"amount": arguments[3]
}
} else {
var payload = {
"nonce": nonce,
"command": command
}
}
NOTE: this is expecting the call to poloniex() function for a "buy" to be: =poloniex("buy","currencyPair",rate,amount) for example: =poloniex("buy","BTC_ZEC",0.01,2) Finally, I suspect that attempting to use a Google Spreadsheet may not be the best idea... it is quite possible that whenever the sheet is recalculated, that any cell you have with =poloniex() will be automatically rerun... and you could end up placing multiple buy orders unintentionally!  (or multiple sell orders if you implement that command). |
|
|
|
The OP hasn't been active on the site since the 6th... coming up 2 weeks now with no response...  No great loss either way... and I learnt a little about Tkinter  |
|
|
|
Just be mindful to use the "official" bitmixer.io website. There are/were several known "scam" versions that look very VERY similiar to bitmixer that were not affiliated with bitmixer and scammed a number of users. For the record, the true URL is: https://bitmixer.io/I'm sure this advice holds true for other well known mixers like BitBlender and the new ChipMixer... make sure you are definitely on the correct site before sending coins! |
|
|
|
Seems to work OK here... I just created an account... went to the settings and did this:  for practice, I set the "new" PIN as 12345678... clicked the "Change Secret Pin" button and it started generating new secrets and gave me a new mnemonic.  Are you sure you're only using letters and numbers as specified for the PIN? no special symbols... |
|
|
|
|
3.5K Indian Rupees is ~US$50... while not exactly a "trivial" amount, it certainly isn't going to break any records as the largest loss due to bitcoin scammers.
If you are accepting reversible payment methods in exchange for non-reversible bitcoin, then that is obviously a risk you have decided to accept... Perhaps you may need to rethink your business model and the use of Escrows to avoid similar occurences in the future?
|
|
|
|
It's hard to see where the appropriate values are being set... ie. "currencyPair", "rate", and "amount". Have you tried debugging the value of payloadEncoded? As this would appear to be where the values for the "currencyPair", "rate" and "amount" values are being set (I assume from cells in the spreadsheet?  ): var payloadEncoded = Object.keys(payload).map(function(param) {
return encodeURIComponent(param) + '=' + encodeURIComponent(payload[param]);
}).join('&');
Can you dump the value of payloadEncoded to the console and make sure that your parameters are actually being included properly... Also, your "poloniex" function only takes 3 parameters... but you're sending 4? function poloniex(command,parameter,subparam) vs =poloniex("buy","BTC_ZEC",0.01,2) |
|
|
|
|
If you still have the original version of the wallet.dat file that you copied over from your Mac, (ie. it hasn't been opened in Bitcoin Core) then there is no reason why you shouldn't be able to recover the coins.
The only way you are likely to have lost the coins was if your wallet was an old style non-HD wallet (ie. created before Bitcoin Coin v0.13)... and you created a transaction that resulted in change being placed into a new generated change address that was beyond the limits of the original 100 pool addresses... and then you lost that updated wallet.dat.
So when you check the address on blockchain.info it is still showing your 0.14 btc balance correct? All you should really need to do is let Bitcoin Core fully sync up and then shut it down. Make a backup of whatever wallet.dat you currently have in the Core data directory (on windows this defaults to %appdata%\Bitcoin unless you set a custom directory during install/setup). After you have backed up the exisiting wallet.dat, make a copy of the wallet.dat from your mac and place this copy into the Core data directory and then restart Bitcoin Core.
It should start up and you should then be able to see the transactions/addresses and coins from that wallet.dat. If you get nothing, then you'd definitely need to post up the debug.log contents... it really shouldn't be so big that it can't fit on pastebin... if it is, just copy the entries from the bottom of the file dated when you try and use the imported wallet.
|
|
|
|
Ok... so at this point I would probably do something like the following: - 1. Setup TREZOR as required (if you want to use Electrum, go for it) and generate a receiving address.
- 2. Install and Setup Bitcoin Core. DO NOT use your old wallet.dat at the moment, just create a "dummy" wallet. At this stage I'd also recommend setting the Display Units to "BTC" just to avoid any confusion later (Settings -> Options -> Display -> Units to show amounts in)
- 3. Run Bitcoin Core and let it sync up to at least when you stopped using your wallet (ie. Let it sync until say 2012 or 2013 just to be safe if you think you stopped 6 years ago). This actually shouldn't take very long.
- 4. Shut down Bitcoin Core
- 5. Disconnect from ALL networks
- 6. Make a copy of your wallet.dat from the USB and put it in the Bitcoin Core datadir (By default, on windows this should be %appdata%\Bitcoin unless you changed it during install/setup), overwriting the default wallet.dat that would have been created during install/setup.
- 7. Start Bitcoin Core. It will likely need to spend a few minutes rescanning (but not redownloading) the blockchain for the transactions for your wallet. Once complete, you should be able to see all your coins, addresses and transaction history etc.
- 8. Once you can see all your coins, you can create a "test" transaction that sends a small amount of coins to your new TREZOR. Be mindful not to send "dust"
 - 9. Re-connect to the internet to broadcast the transaction and then disconnect again. (see notes below for alternatives)
- 10. Once you are satisfied that the TREZOR is working as it should be with your "test" transaction, you can then create a transaction that sends ALL your coins to your TREZOR (either the address from Step #1 or create a new TREZOR address). (see below)
- 11. Re-connect to the internet and send the transaction. (see below)
NOTES:- Please note that the above is just what I would do, if I was in your situation. I don't necessarily recommend that you follow the same procedure. - Step 7, If you don't see your coins or any transaction history, you'll need to check the wallet addresses and see if they still hold coins. ("File -> Receiving Addresses") and check some of the addresses on a block explorer like blockchain.info. Once you find the addresses with coins, make sure that you have sync'd Core up to the last date that these addresses have transactions listed for them. - Step 8, I would recommend that you send at least 0.001 BTC as a test and don't send anything smaller. - Step 9 and Step 11, if you'd rather not reconnect the computer with your wallet.dat on it to the internet, you can simply copy the "raw" transaction onto a USB, transfer it to another computer and broadcast using one the websites listed below. These websites can't do anything "bad" with your already signed transaction, it is no different to broadcasting the transaction to the network yourself.  To get the raw transaction, simply right-click on the new "unconfirmed" transaction in the "Transactions" tab, and select "copy raw transaction". Then paste that data into a text document (it will just be a big long "hex" string of numbers/characters), save the text file onto a USB and transfer to another computer. Then on the online computer, copy the hex from the text document and paste into one of the following: https://coinb.in/#broadcasthttp://blockr.io/tx/pushhttps://live.blockcypher.com/btc/pushtx/https://btc.com/tools/tx/publishSeveral of these sites give you the option to "decode" or "verify" so you can double check the transaction details (output address, amount and fee etc) before broadcasting. - Step 10, I would recommend that you switch on "Enable Coin Control Features" and "Spend unconfirmed Change" in Settings (Settings -> Options -> Wallet). Especially if you sent a test transaction, as you'll no doubt end up with "change" from that test and as your Core won't be sync'd, any change from the test won't be "confirmed" until you let Core sync all the way! When you got to setup the transaction, on the "Send" tab, click the "Inputs" button and then the "Select All" button. You should be able to see the "bytes" value. This will also enable you to work out an appropriate fee. These websites will give you an idea of the fees currently in use: https://btc.com/stats/unconfirmed-tx https://bitcoinfees.21.co/Please note that if you fail to use a "proper" fee, there is a good chance that your transaction (and all your coins) could get "stuck" in an unconfirmed state. I would highly recommend that you let Bitcoin Core calculate a fee for you (Use "Recommended" setting in the "Send" tab and use the slider to adjust to an amount/confirmation time that you are comfortable with)... unless you are 110% sure you know what you're doing setting a custom fee. |
|
|
|
The reason I export my keys is because of this August 1st thing.
What will happen to multibit classic if bitcoin hard forks? My understanding is that (because multibit does not get updated) only one of the 2 chains will show on multibit. This is correct. MBC (MultiBit Classic) is not likely to receive any updates. It is effectively "end of life" and no longer maintained at all. So I need the private keys to be readable from another wallet in case a hard fork occurs.
That's fine, but MBC isn't going to magically stop running and/or not allow you to export your keys if there is a fork. You will still be able to open up MBC and export your private keys in the event of a fork. It will just not be able to deal with both chains. Yes I know having plain text private keys is risky, but are the multibit-encrypted private keys importable to another wallet? Or should I decrypt them first according to the above instructions posted? The encrypted keys are not importable into any other wallets that I am aware of. None of the wallets really support importing encrypted stuff. This is mostly due to there being no real standard for exporting of encrypted keys. Wallets that do this are free to encrypt in any way they like, so it is somewhat unreasonable to expect any wallet to be able to read encrypted files generated by some other app. If you feel you "must" export your keys now, I would highly recommend that you do so using encryption. It will make it less likely that your keys get compromised should you happen to have any unknown malware on your PC. Also, as already noted, there are tools and methods available to allow you to decrypt the file should you need to access them in the event of a fork. |
|
|
|
Thanks for your reply brother. What reasonable value will you suggest for txconfirmtarget=X
I mean what number can i replace with X.
Pretty much any integer number >= 1. From the docs: -txconfirmtarget=<n> If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 6) What does -txconfirmtarget=X mean? Why - added before txconfirmtarget=X
Questions like this indicate that you're probably biting off more than you can chew... the "-" is a standard way of indicating a new commandline argument when you need to also specify options for those arguments... ie. myapplication.exe -arg1 option -arg2 -arg3 -arg4... have you read ANY of the documentation for the applications that you are trying to use to implement your system? In case if i want to set up my own tx fee, normally how many KB would be required to process a transaction(approx)? Can i set up paytxfee=0.00020000
Transaction size in bytes can be roughly calculated using the following formula: (Number of Inputs * 148 bytes) + (Number of outputs * 34 bytes) + 10 bytes You can pretty much use any fee you like. Although you should know that a lot of nodes will refuse to propagate your transaction if the fee rate is too low. If i setup the above value, will the transaction fee for each transaction will be 20,000 satoshis or less?
It should be exactly 20000 satoshis in total. If i use dyanamic fee, what would be the approx fee per transaction? How do i check the approx fee per transaction
How long is a piece of string? No one can answer this for the simple fact that "Dynamic" fees are dynamic... they go up and down to meet the current network conditions... Also, you need to stop considering the fee as a "total amount"... you need to be working on a BTC per kiloByte or a Satoshis per Byte. The total fee has no real affect on the confirmation speed. Miners look at the fee rate. refer: https://bitcoinfees.21.co/ and https://support.21.co/bitcoin#transactions-and-fees for more info regarding fees |
|
|
|
|
How long has it been since you did the transactions? There have been other instances where the ShapeShift transaction from inside a wallet (like Jaxx or Exodus) takes a while. As for where it is going to go, when you did the conversion, what BTC address did you enter? That is where ShapeShift should send the coins.
|
|
|
|
|
Simple test to see if your wallet is suitable for holding coins during a fork:
1. Does your wallet provide you with the private keys for all addresses contained in it?
Yes? Wallet is OK.
No? Wallet is not Ok.
In the situation where your "wallet" is on an exchange/gambling site or other web based service... the answer to 1. is most probably "No".
The thing is, it isn't so much that they're going to steal your coins... it's just that you have ZERO control over which side of the fork your coins end up being on. The exchange controls all the keys... so they can effectively decide which coins you are going to own... they may choose to keep all the altFork coins for themselves, rather than creating another coin balance for you for the forked coins... meanwhile, people with their private keys have the luxury of being able to use coins on either side of the fork as they wish.
|
|
|
|
Remote activation can only happen when when there is something on the victims pc to to allow it to run. You can't magically run things remotely on someone's oc without tricking them into installing something first or it finds an exploit into something they already have installed. Dude go put on your little tin foil hat. Paranoid.
So that whole "wannacry" thing was just a made up story by people being paranoid and nothing to do with exploits in Windows Operating System services then?  Given that there have been so many "0 day exploit" attacks in the past... and no doubt will be more in the future... being a little bit "paranoid" when it comes to valuable (and easily "stolen") digital assets is not necessarily a bad thing. |
|
|
|
This should probably be in the programmers mode discussion thread... Anyway, your script doesn't work with the decimal multipliers because the comparison for checking if the bet is over max is using "equals" instead of "greater than or equals". If you simply change the "if previousbet==maxBet then" to "if previousbet>=maxBet then", the code will work with the decimal multipliers like 2.1x or 2.75x etc |
|
|
|
So, you can setup your TREZOR as per the TREZOR installation instructions. I'm sure it came with appropriate documentation and they have a lot of stuff on their website: http://doc.satoshilabs.com/trezor-user/index.htmlOnce you have it setup, generate a receive address... you'll need it to send all your coins to later. I have not touched my wallet at all. Are these safe ? Sorry I am not tech savvy at all lol can you break this down a little bit ? Would u suggest getting a new computer to do this so its safer ? I do not want my coins online for very long. It is out of my comfort zone what I am transferring however I know having them on trezor will be safer.
So have you received any coins to the wallet or not? And is the wallet sync'd up to the point where you last received coins? ie. can you open Bitcoin Core and see ALL your coins? Is the balance what you expect to see, regardless of the fact that Bitcoin Core may be ~6 years behind in terms of blocks downloaded. If you can see ALL of your coins, you will be able to create and sign a transaction that sends those coins to another address (ie. a receive address on your newly setup TREZOR). Is it okay to set up my trezor and electrum from my own computer I have had for many years using my WIFI. Or should I take an extra step buy a new computer ? I am using windows at the moment also worries me about this virus heart bleed etc etc.
Depends on your personal level of paranoia and the perceived level of risk you are willing to carry. If you think your computer is clean (run malwarebytes, spybot search and destroy, SomeOtherAntivirusAntiMalwareApp etc)... then switch off the WiFi, turn on Bitcoin Core and create and sign the transaction that sends ALL your coins to your new TREZOR address. I'd advise triple checking that the address is correct If you don't then back up all your stuff, re-install a clean OS or use a live linux distro like Tails or buy a new computer... do whatever makes you feel secure. The only person that question is you. Also what about fees ? are there any for moving them onto my trezor ? I do not need to move them to electru, correct ? I can transfer all the to my trezor.
Yes, moving your coins will require fees. Also, fees are a LOT higher than they were 6 years ago. Might pay to make sure you're familiar with 'average' fees these days (ref: https://btc.com/stats/unconfirmed-tx and https://bitcoinfees.21.co/) required for fast confirmation times. No, you don't need to store any coins in an Electrum wallet, you can send them all straight to the TREZOR. |
|
|
|
Is anyone else getting an Uncaught Exception... looks like an SQLite Error of some description... but no idea what is causing it? Uncaught exception: Error: Error: SQLITE_CONSTRAINT: FOREIGN KEY constraint failed INSERT INTO unit_authors (unit, address, definition_chash) VALUES(?,?,?) FDIOwPxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxO2/yE=, HZTYxxxxxxxxxxxxxxxxxxxxxxxxxxxxxCUE,
In case anyone else is getting the same error... I figured out a workaround. The error would appear to be a race condition as suggested by come-from-behind. For some reason, the app is attempting to insert a record into the "unit_authors" table for an address that doesn't exist in the "addresses" table... I suspect because the app is processing things in the wrong order during syncing. Anyway, to get around this error, First, make sure you have a backup! (specifically the C:\Users\YOURUSERNAME\AppData\Local\byteball directory) Then make sure the Byteball app is not running so the DB is not locked. Then use a SQLite DB browser/editor and simply insert a new record into the "addresses" table with the missing address from the exception... this is the 2nd value shown... so in my case the "HZTYxxxxxxxxxxxxxxxxxxxxxxxxxxxxxCUE" record... Start the Byteball app and it should continue For an SQLite DB browser... I used: http://sqlitebrowser.orgDB file location: C:\Users\YOURUSERNAME\AppData\Local\byteball\byteball.sqlite |
|
|
|
|
Show Posts
