-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EOS Block #12
Comments
You can sign transactions with You can take a look at github.com/eoscanada/eosc for a command-line tool to interact.. it's also a great repository of example code for Does this help ? |
Hi , Thanks for sharing this , is it working on nodeos ?Because I read a article where they said about Ram Prices and Cpu Cycles to do the transaction over BlockProducers I am not looking for nodeos , I am looking for real block producing steps. Then I will create a block over the Eos BlockChain by Block producers IPs or there config file . |
This lib cannot create blocks.. that would require a full blockchain implementation which this lib is not. It can sign blocks produced by nodeos. See https://github.com/eoscanada/eos-blocksigner |
mind if I close this ? |
hi @abourget , No still I didnt find any EOS BlockProducers url to mined the block by using any trail ram Price and cpu cycles . I think you didnt replied me what i Asked you . |
@prateektiwari7 If you are looking for an API to retrieve block data from the EOS blockchain. You can use
If you looking to produce block yourself, using the There is also eos-bios that can be used to launch a pre-compiled Configuring it correctly to become part of the mainnet EOS network is beyond the scope of this library. Closing issue, feel free to continue the discussion however. |
Hi
How can I use Original(not nodeos) EOS block Producer Apis to do transactions . Is there any link ?
how can i use eoscanda/Eos-go library to produce original Block on EOS chain .As there is no docs are out from any block producer to use there net to do transaction over EOS chain .
The text was updated successfully, but these errors were encountered: