 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
In addition to the above answer, line 4 of the below code - hash.encode('hex_codec') - is an expression that returns a value, but doesn't change hash, so it's not really doing anything. <snip> Script: import hashlib
header_hex = ("000000110000000000000000051f5de334085b92ce27c03888c726c9b2bb78069e55aeb6f4db18d3ecab87eeb23a56490d5b0b514848d510d409b43f6bbf2b82f55da8db55fd4e31181287bad37d21b7")
header_bin = header_hex.decode('hex')
hash = hashlib.sha256(hashlib.sha256(header_bin).digest()).digest()
hash.encode('hex_codec')
print hash[::-1].encode('hex_codec') <snip> |
|
|
|
I am also getting an error on osx 10.10
Traceback (most recent call last):
File "./hashmal", line 17, in <module>
gui.main()
File "/Users/bbuenz/Programmierung/CryptoWorkspace/hashmal/hashmal_lib/__init__.py", line 14, in main
self.main_window = HashmalMain(self.app)
File "/Users/bbuenz/Programmierung/CryptoWorkspace/hashmal/hashmal_lib/main_window.py", line 38, in __init__
self.dock_handler.do_default_layout()
File "/Users/bbuenz/Programmierung/CryptoWorkspace/hashmal/hashmal_lib/dock_handler.py", line 90, in do_default_layout
self.dock_widgets['Variables'].setVisible(True)
KeyError: 'Variables'
Did you run setup.py? |
|
|
|
Alright, there's now a plugin system. I'm looking for ideas for plugins, so if you have any, please post them. Note that plugin basically refers to one or more tools in the form of dock widgets, which are detachable widgets. The purpose of plugins is to provide extra functionality when you have a certain requirement installed. The proof-of-concept plugin that I'm working on is Pycoin, which provides a GUI for pycoin. Also, there's a "chainparams" system that allows you to specify the format of transactions. For example, in Peercoin and its forks, transactions have a timestamp field after their version field. By selecting the Peercoin chainparams preset, you can deserialize Peercoin transactions, and even set the timestamp for a transaction in the Transaction Builder tool. Anyway, ideas for useful plugins are welcome!  |
|
|
|
It will still work without the ltc_scrypt package. It includes a fallback implementation. Your other issue is unrelated and I'm not sure what's causing it. |
|
|
|
Getting closer to a real 0.2.0a release. I've written about and uploaded screenshots of tools on the Github Wiki. There won't be a changelog until after 0.2.0a since so many things are changing. Here are some key recent changes: - Variables can be substituted into a transaction (see Variables tool documentation on Github wiki).
- Variables can be saved to the config file.
- Some stack log messages are now better (e.g. grammatically improved).
If you'd like to try Hashmal but don't know where you would start, check out the Example Scripts page. |
|
|
|
I'm having difficulty getting it to run. Here's what I'm getting after installing from git on OSX Yosemite. $ hashmal
Traceback (most recent call last):
File "/usr/local/bin/hashmal", line 13, in <module>
import hashmal_lib
File "/usr/local/lib/python2.7/site-packages/hashmal_lib/__init__.py", line 5, in <module>
from main_window import HashmalMain
File "/usr/local/lib/python2.7/site-packages/hashmal_lib/main_window.py", line 8, in <module>
from dock_handler import DockHandler
File "/usr/local/lib/python2.7/site-packages/hashmal_lib/dock_handler.py", line 4, in <module>
from docks.addr_encoder import AddrEncoder
File "/usr/local/lib/python2.7/site-packages/hashmal_lib/docks/__init__.py", line 6, in <module>
import tx_deserializer
ImportError: No module named tx_deserializer
My bad. I hadn't included that file in the list of modules in setup.py. Fixed now. |
|
|
|
Any chance of porting this to Javascript?
Not really, no. The whole thing was designed with Python in mind. Anyway, there are now some basic usage docs here. I've also put in a basic Transaction Deserializer tool which can be upgraded with the functionality talked about earlier in the thread at a later time. The most significant update is that you can now specify a "spending transaction" in the Stack Evaluator, and select one of its inputs. That input's scriptSig will be pushed to the stack before your script starts. "OP_CHECKSIG" and "OP_CHECKSIGVERIFY" should work now. Pretty soon I'll have to start incrementing the version number and providing changelogs. |
|
|
|
Thanks for the feedback. Repo transferred to its new home. We're now in #hashmal on freenode. |
|
|
|
Very nice, thank you!
Should there be a list of the Python dependencies somewhere, like a requirements file?
Yeah, there's a requirements.txt now. Python isn't so bad at all, Electrum is also written in Python and works. ;-) However the Windows version of Electrum is nicely compiled to the one executable file. Do you plan the same?
When it's a little more mature, definitely. |
|
|
|
I hadn't thought of that. It's a good idea, albeit one that would complicate starting Hashmal (e.g. compiling the C++ extension). The current method of stepping through scripts - via re-implementing EvalScript() from python-bitcoinlib - is rather inelegant. I'm also relatively unfamiliar with C++ (as opposed to C) extensions in Python. Anyway, there probably should be a better implementation of script evaluation, so that's currently the only option on the table. First POST and OP congratulations because you just solved a problem that every Bitcoin developer of the past few years has grappled with. I'm definitely going to be checking this out.
Edit: seems like an easy improvement to this is add another field for raw transactions to check that the TX is valid and to inspect the script works as intended. I just noticed what you wrote about multi-sig but should be quite easy to code this (pybitcoin-lib already has all the code.)
Thanks! The thing about CHECKSIG is that the Stack View tool was getting pretty crowded so I didn't put in any way to include a transaction. But you're definitely right in that it wouldn't be very difficult to do. I think the best way to accomplish that is to create a tool called "Transaction Deserializer" or some such, and have it be able to interact with the Stack View tool. I'll give that a shot. Oh man, where were you 2 years ago when I was getting started? I'm wishing good things for this project Thanks for the good wishes. |
|
|
|
First POST and OP congratulations because you just solved a problem that every Bitcoin developer of the past few years has grappled with. I'm definitely going to be checking this out.
Edit: seems like an easy improvement to this is add another field for raw transactions to check that the TX is valid and to inspect the script works as intended. I just noticed what you wrote about multi-sig but should be quite easy to code this (pybitcoin-lib already has all the code.)
Thanks! The thing about CHECKSIG is that the Stack View tool was getting pretty crowded so I didn't put in any way to include a transaction. But you're definitely right in that it wouldn't be very difficult to do. I think the best way to accomplish that is to create a tool called "Transaction Deserializer" or some such, and have it be able to interact with the Stack View tool. I'll give that a shot. |
|
|
|
Hashmal Hashmal is an IDE for Bitcoin transaction scripts. Its purpose is to make it easier to write, evaluate, and learn about transaction scripts. There are very few tools that help people learn about how transaction scripts work; hopefully Hashmal can do this. Demonstration of stack evaluation. Hashmal is intended for cryptocurrency developers and power users. It uses python-bitcoinlib for most of its functionality. Key Features- Write scripts in human-readable form.
- Observe the stack as scripts are executed.
- See explanations of script operations as they are evaluated.
NoticeHashmal is a project in its infancy. Please be careful if you intend to use any scripts you make in Hashmal with an actual blockchain. This is alpha software.You can download Hashmal from Github. |
|
|
|
Any idea when DOGE will be available in Encompass?
Yeah, the upcoming release (0.6.0) will include Dogecoin support, along with some other nice improvements. 0.6.0 should be released on June 21. Does the 0.6.0 release give trezor support to Dogecoin or just bring it into the wallet as an option? If it has trezor support that's awesome! Sorry, we've been almost comically behind schedule due to other stuff happening. Dogecoin is supported for Trezor, yes. Any coin that 1.) Your Trezor firmware supports, and 2.) Encompass has support for is usable in Trezor Encompass wallets. This is true even if you're using unofficial firmware. |
|
|
|
Any idea when DOGE will be available in Encompass?
Yeah, the upcoming release (0.6.0) will include Dogecoin support, along with some other nice improvements. 0.6.0 should be released on June 21. |
|
|
|
I hope you can Add Vanillacoin
because very hard to get more address i need more adress
Vanillacoin...is this it? That looks very interesting. Their whitepaper leaves me with some questions (primarily, how it implements a more energy-efficient Proof-of-Stake system), but it's something I'll try to remember to keep an eye on. How is it "hard" to get more addresses? |
|
|
|
Just tried to download the latest version for Windows but only get a 404 or file not found error.....  The website didn't get updated; I'll bug the website folks about that. You can find the binaries on the Github Release page. Encompass interfaces directly with Trezor, just as Electrum does. It doesn't generate its own keys, etc. That your balance is incorrect is puzzling. What do you mean when you say that "the addresses on the receiving end was a lot"? As lead developer of Encompass, I'll help with any problems you're having since I don't want you to think Encompass is untrustworthy  Well I have recently upgraded window to 8.1, so I will go ahead and download encompass and give it another try and definitely check out some stuff, on dash I had created a wallet and sent a coin over for testing, if it is still available I will think it works great and start using it as my main dash wallet as I just really want trezor support for it. The bitcoin issue is a bit concerning but I think it wasn't getting the most up to date information from the blockchain, it was missing a whole coin, so I will test it out later today and see if I still have that issue. Thank you for the offer of help though, I do appreciate it. No problem, thanks for the reconsideration. That issue is something nobody has ever reported before, so I'd like to hear how it goes. If you need any support, come to #mazaclub on freenode. I'm usually available to help there. |
|
|
|
|
At step 2, you should copy the Master Public Key for the account (or accounts if you use more than the default one) instead of copying addresses. With that master public key, you can generate all of the addresses in that account (there are 2^31 of them so don't worry about running out of addresses).
To get the master public key, click Wallet > Master Public Keys in the menu bar.
Then, with that master public key, you can
1.) start Electrum on an online computer,
2.) click File > New/Restore in the menu bar,
3.) check the radio button that says "Restore a wallet or import keys",
4.) and finally enter your Master Public Key in the blank box that appears after clicking "Next".
If you do that, you'll have a watching-only wallet on the online computer, which means you can see all your addresses, your wallet balance, etc. but cannot spend anything because the wallet doesn't know your private keys. That way, you can always keep track of your wallet (you won't even have to use Blockchain.info since Electrum will tell you about transactions) without risking anything.
|
|
|
|
|
Where is this error coming from? A dialog? Or from your terminal? Is there any more information (what would help most looks like a list of function calls).
|
|
|
|
where to find other coin adress ? i am only see MZC receive adress  Go to Wallet > Change Currency, in the menu bar. |
|
|
|
nice wallet i will try it are you have plan to add Dogecoin ? Yeah, as soon as we get a better grasp on auxpow coin code implementation, we can support auxpow coins like DOGE. |
|
|
|
|
