 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
Bumping in hopes of an answer... I appreciate the help given so far, I just need to understand this one process. I understand, and even if you don't feel like explaining it yourself, could you please point me in the right direction by linking me to a resource or giving me proper google search terms that will explain how: 8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581 becomes: 0xb54909e60352ef3ebdd448b65beda938e103624b207c91229bde6e9ba60351e1 Thank you in advance for any help finding the answer here... |
|
|
|
If I am not wrong, Gridcoin uses the most primitive PoS scheme, aka Peercoin like with certain improvements.
Staking would depend largely on the time coins has been staking in your account. The higher your so called coin age and the higher amounts of coins staking, the higher the chance of a staked block.
So to answer your question it probably doesn't matter once you start the stake process. Just be sure not to spend the stake coins, I think it resets the coin age even if moving from your own address to your another address.
Hopefully someone else more familiar with the process can verify and help you more
That sounds logical, thank you for your help! |
|
|
|
Which coin in particular are you staking. Usually it doesn't matter as the staking process requires you to either hold the coins for long ( unspent period), voting through delegates) or other methods. Without the exact coin/s you are going to stake, I cannot really help you
I am staking for Gridcoin |
|
|
|
|
When I am moving coins to a wallet for staking, is there any benefit staking-wise to sending them in smaller transactions, or in one large transaction or does it make no difference at all as far as staking goes...?
|
|
|
|
Because, when you used the site, you calculated the hash on a single 32 byte value represented in hexadecimal radix.
When you used cmdhashgen, you calculated the hash on a string of 64 alphanumeric characters represented in ASCII.
The site calculated the hash using a 32 byte input of:
0xb54909e60352ef3ebdd448b65beda938e103624b207c91229bde6e9ba60351e1
cmdhashgen calculated the hash of a 64 byte input of:
0x62353439303965363033353265663365626464343438623635626564613933386531303336323 462323037633931323239626465366539626136303335316531
I see... Very interesting, thank you for the clarification. For future reference how does one convert a 64 character alphanumeric hexadecimal representation to the proper 32 byte hexadecimal radix...? In other words, how do I turn: 8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581 into the proper: 0xb54909e60352ef3ebdd448b65beda938e103624b207c91229bde6e9ba60351e1 so it can be passed to cmdhashgen for hashing...? |
|
|
|
You have to put the hex string in the text box on the field labeled "binary hash". Then scroll down and find the one labeled "sha256" and copy the hex string and put that in text box in "binary hash". Then scroll down again and the hash in" sha256" is the hash that you want for step 4
OK, I took the hex string from step 3 (8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581) and ran it through the site which gave me: b54909e60352ef3ebdd448b65beda938e103624b207c91229bde6e9ba60351e1 Then i took that result and ran it through the site again, I got: 5b0e90510294762f4553a6f717a13d5dce4c4aa6137311b950f2ca90ffc9a035 Why is that result different than what I got when I used cmdhashgen to hash the string in SHA256...? Because I took the same string, ran it through cmdhashgen's SHA256 encoder, took that result and repeated but I got: 2897b55427f86f73136d55c1729cb4ce56d72e40e33baf8ca10e9e02cb963434 |
|
|
|
No. You are converting it back to binary. What you just need to do is keep the hex string as it is but instead of hashing it as a string, hash it as bytes. Use the website I posted earlier.
I think I understand what you mean now, I want to convert it to the hex form that looks like: 0x80 0x44 0xD0 0x0F 0x6E 0xB2 0xE5 0x49 0x1C 0xD7 0xAB 0x7E 0x71 0x85 0xD8 0x1B 0x67 0xA2 0x3C 0x49 0x80 0xF6 0x2B 0x2E 0xD0 0x91 0x4D 0x32 0xB7 0xEB 0x1C 0x55 0x81 0xb0 0x92 0x6e 0x9a I'm sure that's not the correct string, but that's what it should basically look like? |
|
|
|
Are you using a programming language for this process?
If so, which language, and which packages or libraries are you using?
I'm not sure if I should be presenting suggestions and examples in javascript, java, C, C++, perl, ruby, php, or something else entirely.
So far, I have been doing all of these steps using basic DOS/batch scripts that I am writing as I go aside from cmdhashgen which is being used for the SHA256 hashing. I have some experience and understanding in VBS, C, C++, perl and php. |
|
|
|
No. You are converting it back to binary. What you just need to do is keep the hex string as it is but instead of hashing it as a string, hash it as bytes. Use the website I posted earlier.
I tried using that website, but it outputs 16 different fields only one of which contains the word bytes and that just shows the same information from step 5 except uppercase letters have been replaced with lower case letters... Is that what I am looking for...? |
|
|
|
So what you have is a hex string which is different from hex bytes. Hex bytes are the human readable form of binary. If you were to convert a set of hex bytes to binary, you would get the 1's and 0's that a computer reads. On the other hand, if you have a string, you have something completely different. At the binary level, each character in the string is a set of bytes, and when you hash the string, you are hashing those bytes, and not the bytes that you actually want which you read in the string. To hash the bytes, you can use this site: http://www.fileformat.info/tool/hash.htm. Enter the hex string into "Binary Hash" field and it will give you the hashes down below. When you hash again, make sure you do the same thing and hash the bytes. Thank you so much for your help, I'm getting closer and closer... OK, so i THINK I have that step figured out... If I'm not mistaken, when I convert the hex string from step 5 back to hex bytes it becomes: 1000 0000 0100 0100 1101 0000 0000 1111 0110 1110 1011 0010 1110 0101 0100 1001
0001 1100 1101 0111 1010 1011 0111 1110 0111 0001 1000 0101 1101 1000 0001 1011
0110 0111 1010 0010 0011 1100 0100 1001 1000 0000 1111 0110 0010 1011 0010 1110
1101 0000 1001 0001 0100 1101 0011 0010 1011 0111 1110 1011 0001 1100 0101 0101
1000 0001 0000 1001 0010 0110 1001 1001 1001 1001 Not really sure what to do from here though... EDIT: I am definitely doing something wrong because when I put in the hex string from step 5 into the Hexadecimal field at http://convertxy.com/index.php/numberbases/ I get: 1000 0000 0100 0100 1101 0000 0000 1111 0110 1110 1011 0010 1110 0101 0100 1001
0001 1100 1101 0111 1010 1011 0111 1110 0111 0001 1000 0101 1101 1000 0001 1011
0110 0111 1010 0010 0011 1100 0100 1001 1000 0000 1111 0110 0010 1011 0010 1110
1101 0000 1001 0001 0100 1101 0011 0010 1011 0111 1110 1011 0001 1100 0101 0101
1000 0001 1011 0000 1001 0010 0110 1110 1001 1010 Which is exactly the same all the way up until the last 8 sets of numbers... |
|
|
|
|
Sorry, I don't understand what you mean by hex bytes...
I have had no formal coding instruction, I am entirely self-taught so I apologize if I am misunderstanding something very basic.
I tried to look up what you mean using Google but could not seem to find anything relevant.
How would I go about convert my hex string to hex bytes...?
|
|
|
|
To convert the last string (step 5) to base58, you just do a normal base conversion. Take the string and think of it as a massive number in base 16. Then you just need to do the standard procedure for converting between bases and convert it to base58. There is a variety of software that will do this because doing it by hand is a major pain. This should help you: https://en.bitcoin.it/wiki/Base58Check_encoding#Base58_symbol_chartThat doesn't seem right... If I take the last string from step 5 and do a normal base conversion from base16 to base58 I get: 4HJYHtf8hkGGruED9DOGJVsF6StV9Qjc7Va98cfB5hUKdgsIij8 I'm supposed to be getting 5JLbJxi9koHHvyFEAERHLYwG7VxYATnf8YdA9fiC6kXMghkYXpk |
|
|
|
For fun, I am attempting to generate bitcoin WIF PrivKeys from random binary strings. I have everything figured out except the final step of converting to WIF using base58check encoding. Here is where I am at: Step 1) Generated random binary string 0100 0100 1101 0000 0000 1111 0110 1110 1011 0010 1110 0101 0100 1001 0001 1100
1101 0111 1010 1011 0111 1110 0111 0001 1000 0101 1101 1000 0001 1011 0110 0111
1010 0010 0011 1100 0100 1001 1000 0000 1111 0110 0010 1011 0010 1110 1101 0000
1001 0001 0100 1101 0011 0010 1011 0111 1110 1011 0001 1100 0101 0101 1000 0001 Step 2) Converted binary string to hex string 44D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581 Step 3) Added 0x80 byte to beginning of hexstring 8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C5581 Step 4) Hashed new hex string to SHA256 encoded string, took result and hashed to a new SHA256 string 2897b55427f86f73136d55c1729cb4ce56d72e40e33baf8ca10e9e02cb963434 Step 5) Took first 4 bytes (checksum) and added them to end of hex string from Step 2 8044D00F6EB2E5491CD7AB7E7185D81B67A23C4980F62B2ED0914D32B7EB1C55812897b554 And this is where I am lost... No matter what information I look up online I can not seem to figure out how to turn the last string into a base58check encoded string to complete the process of turning it into a WIF PrivKey. Thanks to "TP's Go Bitcoin Tests", I know that the end result should be 5JLbJxi9koHHvyFEAERHLYwG7VxYATnf8YdA9fiC6kXMghkYXpk But I have no idea nor can I seem to find a clear, coherent explanation of the base58check process that changed my modified hex string to a WIF PrivKey... To be clear, I want to actually learn how the process works, so please do not just point me at a tool online and say "Just do it here, it is much easier". Thank you in advance to anyone who can help explain this to me! |
|
|
|
|
If you believe that Bitcoin has what it takes to be our next mainstream currency (as I believe) then you can consider Bitcoin in it's infancy.
Speaking from an American's standpoint, one thing we can rest fairly assured of is that fiat currency is on it's way out the door. It's only a matter of time before we move from a paper/coin currency to a completely digital currency. Wall Street and the Federal Reserve would like us to believe that we need tangible currency to trade for tangible goods, but realistically the dollar and all forms of change aren't worth the cotton and metals they are printed on. The dollar was always doomed to fail (it was pretty much designed that way) and it's downfall was accelerated when Nixon took us off the Gold standard in the early 70's making the dollar essentially worthless...
In my opinion it seems self-evident that humanity as a whole will likely eventually move to a completely digital currency for it's advantages in safety, simplicity and the effective cost savings of not having to continue printing and circulating paper/metal currency. At the moment, I believe Bitcoin is the best candidate for a standard digital currency but I also believe there is plenty of room for other niche coins as well. I think there will be many successful coin markets as merchants and services create their own niche currencies.
With those things considered, I believe there's still PLENTY of time to get in on Bitcoin and other interesting choices.
|
|
|
|
**UPDATE: VERSION 1.0.2 RELEASED**
Apr 04, 2016 - Fixed an issue preventing scripts from working with encrypted wallets, improved user experience |
|
|
|
**UPDATE: VERSION 1.0 RELEASED**
New Features:
Added functionality to resend stuck (0 confirmation) transactions
Bug Fixes:
Fixed "SignMessage" and "VerifyMessage" scripts which were not accepting input properly
|
|
|
|
Should you need help with this again in the future, I have released a set of scripts (BATforN - https://bitcointalk.org/index.php?topic=1409955.0) that make various functions easier and/or faster to accomplish including message signing and the scripts work for pretty much ANY coin client. |
|
|
|
Sorry, but why is a batch file wrapper easier to use than the actual wallet?
I agree, it's definitely less user-friendly than using most GUI wallets. Never mind the fact that it doesn't do anything special. As stated in OP, this is for people who are not comfortable using the debug console. This walks them through some of the processes they might otherwise find difficult or intimidating. Many coin clients don't have simple, easy-to-use buttons for all of their features. Someone using a coin client that doesn't have simple, easy-to-use buttons for signing messages, verifying messages, encrypting their wallet, exporting/importing private keys, generating new keypairs, repairing corrupted wallets, checking wallet integrity, validating coin addresses, validating public keys, etc... can find great use from this simple set of scripts. The best part is that the scripts can be used with pretty much ANY coin client. Most wallets do not have easy-to-use buttons for all of their features, this just simply makes those features easier to use. I am a fairly proficient crypto user and I still use automated scripts for a lot of my crypto-related tasks. |
|
|
|
Bitcoin/Altcoin Tools for Newbies - Version 1.0.1**Apr 04, 2016 - UPDATE: Version 1.0.2 Released**INTROBATforN is for the Windows operating system. It has only been tested on Windows 8.1 but as far as I know should work on all Windows platforms. If you encounter any bugs, have any requests, questions, comments or concerns, please let me know. Many coin clients don't have simple, easy-to-use buttons for all of their features. This set of scripts simply makes those features easier to use. Someone using a coin client that doesn't have simple, easy-to-use buttons for signing messages, verifying messages, encrypting their wallet, exporting/importing private keys, generating new keypairs, repairing corrupted wallets, checking wallet integrity, validating coin addresses, validating public keys, etc... can find great use from this simple set of scripts. The best part is that the scripts can be used with pretty much ANY coin client. BATforN started as a way to make my own Bitcoin/Altcoin tasks faster and easier to accomplish. As I progressed, I decided I would release my files for public use and so I have also added scripts that I thought might be useful for people who are either new to Bitcoin or just less tech-savvy in general. If you're not comfortable with using the debug console, you find the debug console confusing to use, etc... then this tool will likely be helpful for you. I will continue to improve and add features. All elements of BATforN are entirely open-source with the exception of "coind". If you do not trust my daemon then you can replace it by going to http://bitcoin.org, download either the 32 or 64 bit ZIP package of the Bitcoin wallet, extract the downloaded folder, open the "bin" folder inside, rename "bitcoin-cli" to "coind" then copy to "BATforN\Scripts" and overwrite the old file. Once done, you can delete the rest of the downloaded Bitcoin files. To view the source code for any of the scripts, simply right-click the script and select "Edit". Do NOT make/save any changes or you can/will break the script. CURRENT FUNCTIONSBackup Wallet to Location Check Wallet for Integrity Dump Private Keys Encrypt Wallet Get Balance Get Client Info Get Mining Info Get Peer info Get Raw Transaction by TXID Get Staking Info Get Subsidy Get Transaction by TXID Help Information Returned by Coin Client Import Private Keys List Accounts in Your Wallet Make a Public/Private Keypair Repair Corrupted Wallet Resend Stuck (0 Confirmation) Transactions Sign Message With Address Stop/Exit Coin Client Validate Coin Address Validate Public Keys Verify Signed Messages USAGEStep 1: Configure BATforN for your coin of choice by running the "Run_First" file. If you have more than one coin, you MUST run the "Run_First" file before working with each new coin. Follow the prompts & enter requested information. Step 2: Open the "Scripts" folder and run the appropriate script for the task you wish to accomplish. Follow the prompts and enter information if requested. VirusTotalhttps://www.virustotal.com/en/file/7247a8bded0ae9a8e27bf2c04eca470f7a003665319d09ac1ec7a64f7798b5e3/analysis/1458821115/DOWNLOADhttp://github.com/ExabyteMiner/BATforNCHANGELOGApr 04, 2016 - Fixed an issue preventing scripts from working with encrypted wallets, improved user experience Mar 25, 2016 - Made script output more descriptive, Made code cleaner/less redundant Mar 24, 2016 - Fixed "SignMessage" and "VerifyMessage" scripts which functioned improperly with whitespaces, added functionality to resend stuck transactions Mar 23, 2016 - Initial Release |
|
|
|
|
Really enjoying this coin! Just wanted to point out, in the sample.conf in OP you have "reservbalance" instead of "reservebalance".
|
|
|
|
|
