This is M1r4c13, a brand-new site by Miracle Yu that reborn from the previous xhyumiracle website, after offline for 7 years.
Many things changed, my focus also changes from security to crypto * (zk + ai). Hope I can bring you some more interesting facts in this new world.
Things will be up and running here shortly, but you can subscribe in the meantime if you'd like to stay up to date and receive emails when new content is published!
1. Download the client from here, or use the following Shadowsocks-4.4.1.0Shadowsocks-4.4.1.0.zip4 MBdownload-circle 2. Download OBFS plugin here, or use the following obfs-localobfs-local.zip170 KBdownload-circle 3. unzip the obfs-local.zip, put both files in the same directory with shadowsocks.exe 4. right-click shadowsocks taskbar
Before Start I wrote this series of posts to remind myself the way I analysis EOS src code. My purpose was to learn security handling in C++. I'll update posts as I analyzing it, so maybe it lacks of construction, forgive me on this if it does. nodeos
pre-requisite This part assumes you've created at least one account. If not, please check the previous post EOS Dev Guide 0x02. Compile contract contract needs to be first compiled to .wasm format as a bin file. Then generate the .abi file to serve as a function interface index
Prerequisite This part assumes you've booted up the private net(nodeos) and had it kept producing blocks. If not, please check the previous post: EOS Dev Guide 0x01. Deploy eosio.bios contract This step needs nodeos to be running and producing blocks. We need to deploy eosio.bios