HelloZeroNet
ZeroBlockChain My idea.... and first implementation (not final)
Sorry for so much opened issues from my site....
It is of course far from finished, but this is my first successful attempt to rewrite the Github project for ECDSA addresses https://github.com/codebox/blockchain, it takes the libraries directly from Zeronet for key generation.
Now here it is https://github.com/wolfitdm/blockchain ... i have much to do here
Rewriting VerifyID is more difficult than expected, as it is a dart project that was deployed as a web application and the code is so beautifully obfuscated.
So you would have to recreate it here.
But I still like the idea that the data for the resolvers etc. can also be exchanged via blockchains, or that ZeroID can also be mapped. No idea, I still have to think about that.
I am also still in the process of adding some kind of support for yo domains to ZeroNameEx, as NameYo no longer works for me, or I have to see how far I get there.
Otherwise, ZeronameEx is running stably.
New results
Yay i now have my own json chain
The addresses and the blockchain are all json files, and really easy to share....
Not so lock indexes and db files like namecoin and still we have a blockchain here.... with a peer to peer network.
THX codebox for your work, but the guy use RSA keys and that was not so cool and the pycrypto package from his project don't work on windows, but not a problem, now we use the libraries from zeronet, and have a full blockchain without additionally dependencies
The pem files are not really pem files, it are json files the have the file extension pem haha, i think i change that in the future
for example super.pem
{"name": "super", "pubkey": "sorry but you can not see my pubkey", "privkey": "privkey in wif format but sorry i can not share my private key", "key_file_path": ".\super.pem", "address": "1JyWJi8jqswBZxTxmSDV2S9dXfwn6imfea", "key_format": "pem"}
On files where the hash functions are needed, i use that in order to get access from the zeronet libraries
app_dir = os.path.dirname(os.path.abspath(file)) app_dir = "C:/Users/xxx/Downloads/ZeroNet-win-dist-win64/ZeroNet-win-dist-win64/core" app_dir = os.path.join(app_dir, "../core") #os.chdir(app_dir) # Change working dir to zeronet.py dir sys.path.insert(0, os.path.join(app_dir, "src/lib")) # External liblary directory sys.path.insert(0, os.path.join(app_dir, "src")) # Imports relative to src
i think i make that lines on a central point or i make it configurable....
I have much to do here, but it was possible, that the addresses on the zeronet network can use here...
But this project could be the foundation for being able to map namecoin as a Python zeronet plugin. Of course there is still a lot of work to be done here, but you could send money directly to the addresses here for every zite address and you would have a direct connection from a zite address to a domain. Since you could import the zite address directly here, and unlike namecoin, which is not only used for zeronet, this project could focus directly on zeronet. Here you can also set block sizes so that you can anchor entire resolver names.json here. Since the blockchain itself is just a json file, it is a perfect fit.
I will have to think about everything here.
Now we have a rpc server
py -3.12 -m blockchain.wallet.rpcclient sendMoney mining_rewards 5.00 1DP6hJbMmHVbnpc1tHetkNbtULxFfY9Fpe
and start this server with
py -3.12 -m blockchain.main
Why it that important???
Now you can remotely call functions like RPC functions in namecoin....
Yes my chain use also a RPC server and client like namecoin that does..... but without authoriziation , the next step here
So its possible, that you can write a zite and call functions on the the client site...
Or write plugins the use the rpc interface to call functions...
For example plugins like disabled-ZeronameLocal etc , the make calls to the namecoin chain, the target is, that also make the same calls to my chain.....
current update:
https://github.com/wolfitdm/blockchain