PHP Graphene Node Client [v4.0.10 - v5.0.1]

in utopian-io •  6 years ago  (edited)

php-graphene-node-client

It is PHP API client for Steem/GOLOS blockchain

Github or packagist with MIT license. Author @t3ran13 and active contributor @semasping

In Release v4.0.10

  • upd Reputation tool

In Release v4.0.11

  • New set_string of serializer operation was added;
  • New custom_json operation for broadcast was added;

In Release v4.0.12

  • serializer string critical bug fix

In Release v4.1.0

made by @semasping datails are here

  • GOLOS API was updated for HF 18 (methods updates)
  • phpunit tests

In Release v4.1.1

  • upd nodes for GOLOS connectors
  • fix Bandwidth tool after GOLOS HF 18

In Release v4.1.2

  • critical bug was fixed for abstract connectors in current node

In Release v5.0.1

  • code was updated for Bit-Wasp/secp256k1-php v0.2.1 (made by @milan.amatya13)
  • debugger dockerfile was updated for Bit-Wasp/secp256k1-php v0.2.1
  • new examples for requests in debugger

upd Reputation tool

In function was added two additional parametrs - you can set precision and add number to result. The last needed as users without raw reputation has reputation 25 by default.

New set_string of serializer operation was added

Different types are needed for different broadcast operations.
Current availible types

  • set_string
  • string
  • int16
  • asset

New custom_json operation for broadcast was added

It is one more broadcast operation.
Current availible operation

  • vote
  • comment
  • transfer
  • custom_json

serializer string critical bug fix

It was errors for serializing strings with length 128 symbols as permlink, post body or other strings. It was leading to error "3030000 tx_missing_posting_auth: missing required posting authority". It is fixed.

upd nodes for GOLOS connectors

Nodes was tested and updated.
HTTP

fix Bandwidth tool after GOLOS HF 18

After GOLOS HF 18 some fields names was changed and Bandwidth calculations was broken for GOLOS in tool.

critical bug was fixed for abstract connectors in current node

In scripts with requests to different blockchains can happen request to node from other blockchain.

debugger dockerfile was updated for Bit-Wasp/secp256k1-php v0.2.1

Version of Bit-Wasp/secp256k1-php was updated to v0.2.1 in php-graphene-node-client lib.
dockerfile was updated for debugger to actual.

new examples for requests in debugger

New examples of requests were added to debuger

  • raw transfer operation
  • raw custom_json operation
  • get_block request with class Commands
  • GetOpsInBlock request with single class
  • GetDiscussionsByCreatedCommand request with single class
  • GetDynamicGlobalPropertiesCommand request with single class

all examples see here


It is better with each commit

Commits were done by me in master branch

  • upd Reputation tool
  • added new custom_json operation for broadcast
  • added new set_string serializer operation
  • code refactoring
  • fix bug in string serializer
  • restore get_trending_categories method deleted in pull 14
  • added single class for get_trending_tags api call
  • pull 14 fix: new fields in methods after HF 18 of GOLOS
  • pull 14 fix: new fields in methods after HF 18 of GOLOS #2
  • pull 14 fix: delete get_trending_categories after HF 18 for GOLOS
  • pull 14 fix: phpdoc upd
  • upd Bandwidth tool after GOLOS HF 18
  • upd golos nodes in connectors after HF 18
  • fix Bandwidth tool
  • fix critical bag for abstract connectors in current node
  • upd Bit-Wasp/secp256k1-php to v0.2.1 (last 14 days)

Compare v4.0.10-v5.0.1 with all contributors

Commits were done by me in debug branch

  • new requests examples (last 14 days)
  • upd Bit-Wasp/secp256k1-php to v0.2.1 for dockerfile (last 14 days)

Compare are here

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Thank you for your contribution. Since more than 1 contributors are working on the repository, it's better to create branches and then merge it to the master in that way it will be easier to maintain the codebase.

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.


Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]

hi!
thx for advise)

Hey @t3ran13
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!

Want to chat? Join us on Discord https://discord.gg/h52nFrV.

Vote for Utopian Witness!

thank you!