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

[Zoe] Allow contracts to interact in Units rather than Extents #99

Closed
katelynsills opened this issue Nov 14, 2019 · 1 comment · Fixed by #386
Closed

[Zoe] Allow contracts to interact in Units rather than Extents #99

katelynsills opened this issue Nov 14, 2019 · 1 comment · Fixed by #386
Assignees
@katelynsills
Labels
Zoe package: Zoe
Milestone
Zoe 0.2.0

Comments

@katelynsills
Copy link
Contributor

Zoe and the smart contracts running on Zoe should use Units and UnitsOps rather than Extents and ExtentOps. Units are a labeled extent, so Units is safer to use and eliminates confusion.

The only reason we were using Extents and ExtentOps was at the time, Extents were the only easy way to allow contracts to perform calculations and record-keeping without asynchronous calls to a remote assay. This replaced the peg architecture from Scooter.

Now that smart contracts can import modules, I believe each smart contract can import the unitOps.js module and a local copy of the ExtentOps library and create their own local version of unitOps. They would create their own local version by calling makeUnitOps(label, extentOpsName, extentOpsArgs = []) with a label, extentOpsName, and extentOpsArgs provided by Zoe.
@katelynsills katelynsills self-assigned this Nov 14, 2019
@warner
Copy link
Member

warner commented Dec 2, 2019

this was issue 222 in the old ERTP repo, and part of the "Zoe - immediate future" project

@warner warner transferred this issue from Agoric/ERTP Dec 2, 2019
@warner warner added ERTP package: ERTP Zoe package: Zoe labels Dec 2, 2019
dckc pushed a commit to dckc/agoric-sdk that referenced this issue Dec 5, 2019
@warner
require Node.js v12
02e6df8 
There's a new ordering issue that requires Node.js >= v12.

closes Agoric#99
dckc pushed a commit to dckc/agoric-sdk that referenced this issue Dec 5, 2019
@katelynsills
Update dependencies - run npm outdated and update (Agoric#99)
e2b4e38 
* update dependencies - run npm outdated
* remove react-related airbnb rules (switch to airbnb-base). Fix too many classes eslint error
dckc pushed a commit to dckc/agoric-sdk that referenced this issue Dec 5, 2019
@michaelfig
Revert "require Node.js v12"
6feaf2a 
This reverts commit 02e6df8.

The Node 12 ordering differences were only tickled by a bug in
@agoric/eventual-send v0.2.x.  The new version installed in the
SwingSet dependencies does not have this problem.

fixes Agoric#99
@katelynsills katelynsills added this to the Zoe 0.2.0 milestone Jan 9, 2020
@katelynsills katelynsills removed the ERTP package: ERTP label Jan 10, 2020
@katelynsills katelynsills mentioned this issue Jan 12, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@katelynsills katelynsills

Labels
Zoe package: Zoe
Projects
None yet
Milestone
Zoe 0.2.0
Development

Successfully merging a pull request may close this issue.

Zoe Release 0.2.0 Agoric/agoric-sdk
2 participants
@warner @katelynsills