JSON Standard for Block Producer Information on Antelope (former EOSIO) Blockchains
This is a proposed standard for Block Producer candidates to publish as the URL field of the regproducer action on
the eosio.system contract.
The current revision v1.1.0 adds Zod for schema validation, providing improved type safety and better error messages, while maintaining compatibility with the original JSON Schema.
- v1.1.0:
- Added Zod-based schema validation alongside the existing JSON Schema
- Published as npm package
@eosrio/bp-info-standard - Added improved error handling with detailed validation messages
- Enhanced TypeScript support with full type inference
The current schema.json is compliant with JSON schema Draft 2019-09
- producer_account_name: Name of producer account
- org: {Object}
- candidate_name: Producer/organization name
- website: Block producer website
- code_of_conduct: Full URL to page,
- ownership_disclosure: Full URL to page,
- email: Contact email
- github_user: Operational GitHub username (or array or usernames)
- chain_resources: Website with chain related resources (snapshots & backups)
- other_resources: [Array] - List of other relevant URLs
- branding: {Object} - Logo images
- logo_256: Entire url to image 256x256px
- logo_1024: Entire url to image 1024x1024px
- logo_svg: Entire url to image svg
- location: {Object} - Organization location
- name: Location in human-readable format [City, State]
- country: Country code [XX] in accordance to ISO 3166-1 alpha-2
- latitude: Latitude in decimal degrees
- longitude: Longitude in decimal degrees },
- social: {Object} - NOT THE ENTIRE URL, only usernames on social networks,
- keybase: Username
- telegram: Username or group
- twitter: Username
- github: Username
- youtube: Channel address
- facebook: Page/group address
- hive: Username without @
- reddit: Username
- wechat: Username
- nodes: [Array]
- location: Node location
- name: Node location in human-readable format [City, State]
- country: Node country code [XX]
- latitude: Node latitude in decimal degrees
- longitude: Node longitude in decimal degrees
- node_type: Type of service
producer/query/seedor an array of choices["query","seed"]- producer: Node with signing key
- query: Node that provides HTTP(S) APIs to the public
- seed: Node that provides P2P access to the public
- full:
true/falseIndicates if the data is provided since the first block or trimmed at some point - p2p_endpoint: Leap P2P endpoint
host:port - api_endpoint: Leap/Service HTTP endpoint
http://host:port - ssl_endpoint: Leap/Service HTTPS endpoint
https://host:port - features: [Array]
- features supported by the
api_endpointorssl_endpointon query nodes, refer to the list of features
- features supported by the
- metadata: {Object}
- feature key: {Object} - Metadata for a specific feature
- location: Node location
Create a file named bp.json in the root of your domain. For instance https://yourwebsite.com/bp.json When you
register your producer using the system.regproducer action, the url field should be filled
with https://yourwebsite.com. Do not put the bp.json file in the url.
The recommended way to specify multiple bp.json files under the same domain is to use the a chains.json file pointing
to each <chain>.json file according to the chain_id, for example:
{
"chains": {
"aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906": "/bp.json",
"1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4": "/wax.json",
"4667b205c6838ef70ff7988f6e8257e8be0e1284a2f59699054a018f743b1d11": "/telos.json",
"21dcae42c0182200e93f954a074011f9048a7624c6fe81d3c9541a614a88bd1c": "/fio.json",
"38b1d7815474d0c60683ecbea321d723e83f5da6ae5f1c1f9fecc69d9ba96465": "/libre.json",
"0000000000000000000000000000000000000000000000000000000000000123": "/other_chain.json"
}
}It's posible to not include the slash on the sub-url value, as it is implied we are building an url.
You can also override properties of the base bp.json file by creating a chain specific json file next to your base.
--/
----index.html
----chains.json
----bp.json
----chainA.json
----chainB.json
----bp.${chain_id}.json
----bp.aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906.json
The bp.json and bp.${chain_id}.json will be merged and any property inside of the chain specific json file will
override the base properties.
For query type nodes one or more features from the list below must be added:
chain-api: basic eosio::chain_api_plugin (/v1/chain/*)account-query: (/v1/chain/get_accounts_by_authorizers)history-v1: (/v1/history/*)hyperion-v2: (/v2/*)dfusefio-apisnapshot-apidsp-apiatomic-assets-apilight-apiipfsfirehosesubstreams
One can check for data validity using: https://www.jsonschemavalidator.net/
This package can be used as a library to validate BP information in your JavaScript/TypeScript projects.
npm install @eosrio/bp-info-standardimport { BPInfoSchema } from '@eosrio/bp-info-standard';
// Your BP information object
const bpInfo = {
producer_account_name: 'producername',
org: {
candidate_name: 'My Organization',
website: 'https://example.com',
code_of_conduct: 'https://example.com/code',
ownership_disclosure: 'https://example.com/ownership',
email: 'contact@example.com',
location: {
name: 'New York, USA',
country: 'US'
},
chain_resources: 'https://example.com/resources'
},
nodes: [
{
location: {
name: 'New York, USA',
country: 'US'
},
node_type: 'producer',
full: true
}
]
};
// Validate the BP information
const result = BPInfoSchema.safeParse(bpInfo);
if (result.success) {
console.log('BP information is valid!');
// Use the validated data
const validatedData = result.data;
} else {
console.log('BP information is invalid!');
// Handle validation errors
console.error(result.error);
}import { BPInfoSchema, handleZodError } from '@eosrio/bp-info-standard';
// Your BP information object
const bpInfo = { /* ... */ };
// Validate the BP information
const result = BPInfoSchema.safeParse(bpInfo);
if (!result.success) {
// Format the validation errors
const errorMessages = handleZodError(result.error, {
logToConsole: true,
originalObject: bpInfo
});
// Display the error messages
errorMessages.forEach(message => console.log(message));
}For more information about Zod schema validation, refer to the Zod documentation.