Office Hours: patterns of cooperation without vulnerability #22
Comments
This comment has been minimized.
This comment has been minimized.
|
11 Sep notes... Validator Hardware Requirements, Performancekc-strip on devnet: no joystruggled to get my kc-strip node set-up working on devnet https://gist.github.com/dckc/b2823f801f72fdc2a69bb07572141396 was due to version mis-match, I think. but then with 6.0.0 65cec90 https://github.com/Agoric/agoric-sdk/releases/tag/%40agoric%2Fsdk%406.0.0 , I got |
dckc
changed the title
|
Thanks for hosting today, @jimscarver . Good to see you @9rb . Thanks for all the questions that prompted me to provide much better context, @cwebber . As we discussed, it should make the recording much more valuable. And @Bill-Kunj put in an appearance toward the end. Raw tab dump follows; here's hoping I find time to edit these notes. Demo (internal) of RUN protocol governance · Issue #4348 · Agoric/agoric-sdk: Agoric/agoric-sdk#4348 |
|
Thanks for hosting again, @jimscarver After a bit of introductions, we did get around to your request to discuss building a [RChain] token exchange and cross chain/shard swaps using agoric. And I showed a recording of the "start the Agoric economy" governance process demo that didn't quite work last time. raw tab dump follows dckc/awesome-ocap: Awesome Object Capabilities and Capability Security: https://github.com/dckc/awesome-ocap#os |
|
|
comment planned to be subject to edits topic dump related to hardened js / Zoe contract testing.
Seems like a lot of boilerplate code is used. wondering if it would be effective to take an approach in which a test-specific code is embedded within an abstract data type in order to provide an interface for handling Zoe test setup. const { zoeService: zoe, feeMintAccess } = makeZoeKit(fakeVatAdmin.admin);
const bundle = await bundleSource(contractRoot);
fakeVatAdmin.vatAdminState.installBundle('b1-contract', bundle);
const installation = await E(zoe).installBundleID('b1-contract');
const { creatorFacet, instance } = await E(zoe).startInstance(
installation,
issuerKeywordRecord,
terms,
);
// In case a second zcf is needed
const { creatorFacet: creatorFacet2, instance: instance2 } = await E(
zoe,
).startInstance(installation, issuerKeywordRecord, terms);
|
|
Looks like the agoric-sdk -> endo migration is in endojs/endo#506 , Agoric/agoric-sdk#4427 and points nearby. |
|
today's topics, mostly:
tab dump: |
|
|
This week (2 Apr) @Bill-Kunj and @TheoXD have an RDrive thingy to show and tell. Part of the https://github.com/r-publishing stuff, I gather. |
|
raw tab dump from today follows; here's hoping I manage to edit the story a bit... dckc/awesome-ocap: Awesome Object Capabilities and Capability Security: https://github.com/dckc/awesome-ocap |
|
recording: 00:00 smart contract use case: administrative process automation tab dump for today: Office Hours: patterns of cooperation without vulnerability · Issue Agoric/testnet-notes#22 · dckc/awesome-ocap: #22 |
|
tab dump from today: Office Hours: patterns of cooperation without vulnerability · Issue Agoric/documentation#22 · dckc/awesome-ocap: #22 Use WalletConnect · Issue #2962 · Agoric/agoric-sdk: Agoric/agoric-sdk#2962 |
|
Can we discuss the DCF grant proposal in the morning meeting. Would another time be better? Radically decentralized cooperation at scale The aim of this project is user centric voluntary cooperation by consent among autonomous individuals and groups at scale in spite of differences in language, political, religious or philosophical disagreements employing patterns of successful decentralized organization and collective intelligence best practices. Reification and ownership of capabilities with conditional delegation can facilitate capitalization on the abundance of underutilized human potential Regenerative economics (UBI plus cooperation/value incentives?) enables viability of the user centric system. |
|
Perhaps another week. Tomorrow I'm not available. |
Occasional Saturdays 9am Chicago
May 7: Jim's zoom room
See also: Wednesday Agoric Dev Office Hours
Topic Candidates
The text was updated successfully, but these errors were encountered: