antelope
antelope copied to clipboard
wharfkit
Core types, client interfaces, and other tools for working with Antelope-based blockchains.
Just stumbled into this in a nodejs project, when setting `"target": "esnext"` in the `tsconfig.json`, it prevents some structs from rendering properly. Sample code: ```ts const sample = '80b1915e5d268dca000000000090b1ca01000000403290b1ca00000000a8ed3232e2e1006500000000000000000000017055cb2a5fd5b2ca000000572d3ccdcd01000000403290b1ca00000000a8ed32322a000000403290b1ca00000092019ca65e010000000000000004555344540000000954657374206d73696700' @Struct.type('propose')...
when I'm trying to create an account using wharfkit/antelope library, I get the following response from the transaction broadcast. ``` { transaction_id: '41e2edec3278acba808ee6d9b761786be3862af336dc17f6732319ec893d2a01', processed: { id: '41e2edec3278acba808ee6d9b761786be3862af336dc17f6732319ec893d2a01', block_num: 351244143, block_time:...
https://eos.greymass.com/v1/node/get_supported_apis Missing as of Nov 2023 (3.x) - [ ] /v1/chain/get_block_info - [ ] /v1/chain/get_code - [ ] /v1/chain/get_code_hash - [ ] /v1/chain/get_currency_stats - [ ] /v1/chain/get_producers - [x] /v1/chain/get_raw_abi...
Creates a nicer error message, like: 
The ESR library is outputting the embedded ABIs in the payload by default, due to its half-implementation of the Antelope library and its own types. We need to make it...
We frequently find the need to clone a core type as not to mutate it for the caller. Add a .clone() protocol requirement and implementation to all core types.
It would be cool if antelope IBC data types will be added as typescript types for proofs and related interfaces with bridge.
Not sure what they all are yet, but do know a `v1/chain/send_read_only_transaction` will exist. Need to get release notes and see what changed, then add them in.
The error created from an error response from API calls is missing and not printing extra information in the `json.error.details` object that would be useful for developers to see. Only...
With the new k1_recover intrinsics launching, I need a way to get uncompressed keys from @greymass/eosio Seems recover and getPublic both compress the keys Plus there is no uncompressed publickey...
