RPC Provider Model
EVM Network RPC Provider Data Model Documentation
Last updated
EVM Network RPC Provider Data Model Documentation
Last updated
requirements
format: more than 0 characters & less than 41
standard: official name to identify RPC provider & unique [in providers data set]
requirements
format: more than 0 characters & less than 21
standard: short name that identifies RPC provider & unique [in providers data set] & exact to the object instance key
requirements
format: start with 'https://' & have more than 9 characters
standard: must use HTTPS protocol
requirements
format: -
standard: service must have front-running protection to be set true
requirements
format: privacy | partial privacy | no privacy | no info | null
standard: quantify by level the privacy protection offered by the RPC service provider
requirements
format: start with "https://" & have more than 9 characters
standard: must use HTTPS protocol
requirements
format: more than 3 characters and less than 251 characters
standard: must summarise the privacy policy sources
requirements
format: key in (twitter | linkedIn | youtube) & value an HTTPS endpoint
standard: must use HTTPS protocol & endpoint start with associated base HTTPS URL
twitter base endpoint URL: https://twitter.com
linkedIn base endpoint URL: https://www.linkedin.com
youtube base endpoint URL: https://www.youtube.com