# EVM Runtime base token

**URL:** <https://gov.near.org/t/evm-runtime-base-token/340>\
**Category:** Governance\
**Created:** [January 6, 2021, 3:49pm UTC](https://gov.near.org/t/evm-runtime-base-token/340 "2021-01-06T15:49:46Z")\
**Posts on this page:** 1\
**Showing post:** 38

<div class="post-metadata">

**Author:** ![tahpot](https://dub1.discourse-cdn.com/flex005/user_avatar/gov.near.org/tahpot/32/339_2.png) [@tahpot](https://gov.near.org/u/tahpot)\
**Post date:** [January 28, 2021, 12:17am UTC](https://gov.near.org/t/evm-runtime-base-token/340/38 "2021-01-28T00:17:52Z")

</div>

JSON is a standard: [Information on RFC 8259 » RFC Editor](https://www.rfc-editor.org/info/rfc8259)

While not the focus of conversation here, it would be incredibly useful to support JSON for other reasons beyond ERC token support.

JSON is the basis of [Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) and [confidential storage](https://identity.foundation/confidential-storage/) which are emerging data standards. The ability to leverage this off-chain JSON data for inputs into smart contracts will be incredibly powerful.

---

_[View the full topic](https://gov.near.org/t/evm-runtime-base-token/340)._