Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Handle context-free data #535

Merged
merged 1 commit into from
Apr 16, 2019
Merged

Handle context-free data #535

merged 1 commit into from
Apr 16, 2019

Conversation

tbfleming
Copy link
Contributor

Change Description

Add support for context-free data in transactions. Signature providers may optionally support this. eosjs-jssig.ts supports it.

API Changes

  • API Changes

Several functions and interfaces now have optional fields for handling context-free data.

Documentation Additions

  • Documentation Additions

Overview of context-free actions and context-free data:

  • Context-free data is an optional transaction field containing bytes[] (array of array of 8-bit values)
  • Context-free actions in contracts may reference this data, but normal actions may not
  • Context-free actions are similar to normal actions, but may not reference state. This includes, but is not limited to: tables, authorizations, current time, etc.
  • ABI 1.0 and ABI 1.1 do not describe context-free data; it's opaque
  • ABI 1.0 and ABI 1.1 do not distinguish between normal and context-free actions. It's up to users to know which is which, and place them in the appropriate transaction member (actions or context_free_actions)

@tbfleming tbfleming merged commit 8ca3a69 into develop Apr 16, 2019
@tbfleming tbfleming deleted the context-free branch April 16, 2019 14:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants