Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FATIP-S Smart Contracts and Supporting Standards #33

Open
wants to merge 11 commits into
base: FATIP-0-Enable-Zero-Input-Transactions-Send-To-Self
Choose a base branch
from
Open

FATIP-S Smart Contracts and Supporting Standards #33

wants to merge 11 commits into from
+480 −6

Conversation

drkatz
Copy link
Member

@drkatz drkatz commented Sep 21, 2019

This commit lays the base for contracts on FAT:

  • Specifies necessary changes to FAT-0, validation, operation needed to facilitate publishing and calling contracts
  • Proposes a new supporting standard FATIP-104 which describes how contracts should be published to a chain, and how their ABI must be specified for usage by our system.
  • Proposes a new supporting standard FATIP-105 which describes the in-contract interface for retrieving context info from the host and performing key operations for contracts

Base work and first pass of contract modifications and additions

Verified

This commit was signed with the committer’s verified signature.
martin-sucha Martin Sucha
SSH Key Fingerprint: TcKxeY58a0HRfycY4dCuqMF23FrNyEcclOdVzUI9BBI
Verified
Learn about vigilant mode
03c941b
@drkatz drkatz changed the base branch from master to FATIP-0-Enable-Zero-Input-Transactions-Send-To-Self September 21, 2019 05:25
@drkatz drkatz mentioned this pull request May 20, 2020
Open
Merge branch 'FATIP-0-Enable-Zero-Input-Transactions-Send-To-Self' in…
a0724e3 
…to FATIP-S-Smart-Contracts-And-Supporting-Standards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@drkatz @AdamSLevy