During installation of demo.rhobot.net, it was discovered that some third-party tools are used that are not part of the basic Ubuntu build. These should be added to the bootstrap documentation.

How does this work?

https://github.com/rchain-community/liquid-democracy/blob/60d7365f2776695babc9f0304e56dac80a4e34f4/Community.rho#L60

Sometimes the contracts return maps:

     capabilities!({"read": bundle+{*read},
       "write": bundle+{*write},
       "grant": bundle+{*grant}}) |

-- https://github.com/rchain-community/community/blob/master/directory.rho#L5-L7

other times they return channels with "method suites":

      contract self(
        @"get",
        @{signature /\ String},
        @{nextNonce /\ String},
        getReturn
      ) = {

-- https://github.com/rchain-community/community/blob/master/locker.rho#L102-L107

The latter seems to fit more straightforwardly with traditional ocap patterns better.

See also librho style guide discussion from Oct 2018 JoshOrndorff/librho#7

participate.js has been changed to fetch actions from .rho files instead of getting them from the actions.js file
fetching the .rho files works, but the text box in the web UI no longer updates with the selected action unless the "explore" button is pressed.

since we now have sepate files for each action the build command for netlify need to be updated when we do the merge to master.

npm run build; cp -pr src/actions dist/

I gather this is in progress; http://rhobot.net:8888/ https://rgov.rhobot.net/ have a rhobot network option.

When I first went to https://rgov.rhobot.net/ I ran into:

rnode.js:63 Mixed Content: The page at 'https://rgov.rhobot.net/' was loaded over HTTPS, but requested an insecure resource 'http://rhobot.net:40403/api/explore-deploy'. This request has been blocked; the content must be served over HTTPS.

Perhaps this part is actually working. But reportedly "everything broke" and it's not clear to me whether the problem was in the back end network (#55) or this one.

@jimscarver @Bill-Keuntje is it clear who has the ball on this? Would you please nominate someone by assigning them?

I gather that part of the preparation for a demo yesterday was setting up a network, but "everything broke" in some way.

@Bill-Keuntje says

Current theory is we didn't have latest code.

Large parts of Ballot.rho look awfully familiar. I think I wrote them. I strongly prefer preserving git history so git blame works, but at least add something in the "initial commit" message and/or the code itself. I guess I could, but it would be a lot easier if you cited the source from which you copied it, @jimscarver

In case, I sound like a broken record, get used to it. :)

perhaps as a way to advertise public keys? hm.

https://w3c.github.io/did-core/#core-properties

until the performance of testnet is improved there is a need for a more performant test shard.

rhobot.net may be added as a fourth choice in the network dropdown. It may be used to trial rgov community features like usernames, CrowdFund, WorkGroup, etc. with real users

This can initially be stand alone for the best performance. Later we can allow developers to bond with the rhobot.net shard.

https://github.com/rchain/rchain/blob/ce55a8adc349c05f62fb94fa028138ab93c71780/rholang/src/main/rholang/cross-shard.rho

The model of mailboxes and ballots could be used with tickets / unforgeable names

very much like castVote.rho

add testvote.rho test.sh?

It's not used as far as I can tell.

https://github.com/rchain-community/rho-bot/blob/f532b2e636c6c6dc6d940fa0e8e0d51d5e603c77/Community.rho#L8

MacRhoBot is running in colab discord. To see the rholang of a macro on discord type:

show: macroname
or to fully expand imbedded macros
echo: $addmember(community,user)

find:

$add2Directory($name,$key,$value,$ret)
$addmember($community,$user)
$addUser($username,$directory)
$allowalltovote($community,$ballot)
$allowtovote($user,$ballot)
$chat($user,$message)
$makemylocker
$membersOf($community,$return)
$mydefaultdelegate($community,$username)
$mydelegate($ballot,$username)
$newBallot($name,$choiceSet)
$newCommunity($name)
$newDirectory($name)
$newinbox
$peek($types_return...)
$readchat
$readDirectory($name,$arg_ret...)
$readDir($name,$arg_ret...)
$receive($type,$subtype_return...)
$send($user,$list...)
$share($username,$type,$subtype)
$vote($ballot,$vote)
$voteresults($ballot)

see rchain-community/rchain-api#79

@jimscarver notes there is no good video on adding actions, we need to make one..

• 2020-10-27 RChain Rholang Community contracts experiment covers some rholang
• 2020-09-13 RChain dev tool development and liquid democracy develop... talks about the build environment and creating collective intelligence

If the user has just entered a value in a field and immediately clicks "Deploy", the deployed code is not updated with the value from the field.

Feb 27 office hours recording

tab dump:

dckc/finquick: web app access to gnucash financial data: https://github.com/dckc/finquick
jessica/quasi-jessie.js.ts at master · dckc/jessica: https://github.com/dckc/jessica/blob/master/lib/quasi-jessie.js.ts
rchain-community/liquid-democracy at react: https://github.com/rchain-community/liquid-democracy/tree/react
Liquid Democracy Participation Experiment: https://rgov1.netlify.app/
Try js2rho: http://localhost:8888/try-js2rho.html
Try js2rho: http://localhost:8888/try-js2rho.html
Agoric DEX tools: ERTP, Zoe, ... · Issue #4 · rchain-community/js2rho: rchain-community/js2rho#4
SealerUnsealer · dckc/awesome-ocap Wiki: https://github.com/dckc/awesome-ocap/wiki/SealerUnsealer
support W3C DID document format? keybase style follow, proof? · Issue #22 · rchain-community/liquid-democracy: #22
how to read web pages from rholang smart contracts? build a market for consensus (oracle) · Issue #28 · rchain/hackathon-2020: rchain/hackathon-2020#28
Dan Connolly on Twitter: "🦄Verifying myself as a @uniswapprotocol #UNIDelegate on Sybil🏛️ https://t.co/YTCgg2xVY0 addr:0x3dA3050208a3F2e0d04b33674aAa7b1A9F9B313C sig:0x195274576ddb995b7239b8176b0cb540c2dab9879b7d3eec5622d8cae0efd3644fa7561aacad703547734eaba6f123259c5e62d8981a10f5dc52ca88a81a76c91c" / Twitter: https://twitter.com/dckc/status/1362490248039723017
rchain-token/main.rho at ocap · fabcotech/rchain-token: https://github.com/fabcotech/rchain-token/blob/ocap/rholang/main.rho#L97
Issues · rchain/hackathon-2020: https://github.com/rchain/hackathon-2020/issues
Issues: https://github.com/issues?q=archived%3Afalse+user%3Archain-community+sort%3Aupdated-desc+NOT+snyk+
rstake/rstake.md at master · rchain-community/rstake: https://github.com/rchain-community/rstake/blob/master/rstake.md
Rev Define: https://revdefine.io/#/
Governance Proposals on Cosmos Hub | The Big Dipper: https://cosmos.bigdipper.live/proposals
Cosmos | Cosmos Hub 2 | Activate the Community Pool: https://hubble.figment.io/cosmos/chains/cosmoshub-2/governance/proposals/7
Cosmos price today, ATOM live marketcap, chart, and info | CoinMarketCap: https://coinmarketcap.com/currencies/cosmos/
Cosmos Will Have 3 Coding Languages – Here's Why That Matters - CoinDesk: https://www.coindesk.com/cosmos-will-have-3-coding-languages-heres-why-that-matters-for-ethereum

Secure smart contracts - Agoric: https://agoric.com/
MadMode: What's Next: Agoric Computing | Code: https://www.madmode.com/2021/next-gig-agoric.html
Agoric (@Agoric) / Twitter: https://twitter.com/agoric
Cosmos Demo Day: Ethereum Assets on Agoric - YouTube: https://www.youtube.com/watch?v=3arKAQLkm0s
agoric-sdk/issuer.js at master · Agoric/agoric-sdk: https://github.com/Agoric/agoric-sdk/blob/master/packages/ERTP/src/issuer.js
Governance Proposals on Cosmos Hub | The Big Dipper: https://explorer.testnet.agoric.com/proposals
SwingSet Solo REPL Demo: http://127.0.0.1:8000/#
Announcing the Gravity Bridge: https://blog.althea.net/gravity-bridge/

redeploy-class does a propose even if the deploy of the rholang file fails

I suggest changing the liquid-democracy repo name to rgov since it is more encompassing than liquid and not necessarily liquid unless a group wants to be liquid. We call the app rgov in many places. Are there any objections?

https://github.com/rchain-community/liquid-democracy/blob/60d7365f2776695babc9f0304e56dac80a4e34f4/Community.rho#L3

a la https://github.com/rchain-community/rchain-api/blob/master/CONTRIBUTING.md#object-capability-ocap-discipline

cc @jimscarver @Bill-Keuntje

Different voting schemes should be available for liquid democracy.
Right now, the only voting scheme we have is single choice.
Alternative schemes should be "pluggable" into individual issues at the time of creation.

check out Locker using deployerID

The insight is: since rho:rchain:deployerId forms an unforgeable name, no other deployer can refer to it (unless you send it to them, and even then I'm not sure). Likewise compound names built with it. So @[*deployer, "locker1", "put"] is only available to one who holds the deployer key as well.

And the deployer can refer to it in any number of deploys without any registry lookups.

for reference:

• Locker.rho
• Locker_test1.rho

rchain-community/rvote@157eaf4

these are in the rv2020 on a branch just now; I'm not sure where to put them. I'm also not sure of the scope of this community repo, but I see some recent work on the Locker idea here.

cc @jimscarver

The bootstrap binaries need to be on the user's path for ease of use, and the scripts should be executing

cd `dirname $(which $0)`

In the current implementation, "newinbox" can be performed on a system other than the one running the interface. Of course, this fails since "newinbox" requires the ReadcapURI in order to work. When selecting "newinbox", it should be impossible to select an alternative Network in the dropdown.

having explicit code for delegation is sorta silly; we get it for free in rholang.

https://github.com/rchain-community/community/blob/54779fd10ce3ea4e3ee32afeb85ec47b61a962f5/Ballot.rho#L130

create-master-directory.log
I ran across this when using rnode 0.11, not sure if it is an issue for rgov or rnode(alpha)

./deploy-all: Propose finished.
./deploy-all: Generating javascript file [generated.rhoid.bootstrap.js]
./deploy-all: Generating json file [generated.rhoid.bootstrap.json]
./deploy-all: Generating directory creation rholang
Deploying generated.create-master-contract-directory.rho
Parsing error: Error in parsing term:
coop.rchain.rholang.interpreter.errors$TopLevelFreeVariablesNotAllowedError: Top level free variables are not allowed: URI_Directory at 20:15.

URI_Directory is referenced on line 36 of bootstrap/master-contract-directory.sh

create-master-directory.log

@jimscarver did a demo recently (IOU links) but getting the final tally didn't work for what looks like a core dev issue:

• rchain/rchain#3375 deploy fails without error message
  • @jimscarver worked with the core team to diagnose
• demo network #55
• demo front end #56
• land the reorganize-actions branch #45
• rehearsal (again, w/DC)
• demo on a Wednesday debrief (though it didn't actually work)
• recorded demo

reported by @jimscarver in #28 (comment)

I noticed this too. I think I found a fix... either I didn't deploy it or something. not sure.

This is supported in the reorganizing-actions branch

A master directory is created and put under workinggroup.rho (in production) control. A read capability is the only URI that is needed. All the rhain standard contracts and the liquid-democracy/rgov contracts are added.

communities are defined with subdirectories of the master. Each person's locker has a subdirectory of the community directory.

Currently, ReadcapURI should not be checked in to source control. However, the file is updated whenever a bootstrap process is performed, regardless of platform (rhobot, demo, localhost). This leads to easy commit mistakes. A better mechanism of storing the various ReadcapURIs for each platform is needed that does not conflict with source control processes.

https://github.com/rchain-community/community/blob/54779fd10ce3ea4e3ee32afeb85ec47b61a962f5/Ballot.rho#L84

Is this scope of this repo contracts for liquid-democracy? then how about a name to match?

not specific to this repo, but it overlaps

I don't think I have seen this indentation style before. Do you have tools that help maintain it?

I'm in the habit of using scala tools to maintain rholang. (esp. emacs indent-region in scala mode).

https://github.com/rchain-community/rho-bot/blob/f532b2e636c6c6dc6d940fa0e8e0d51d5e603c77/Community.rho#L66-L82

this is supported in the reorganize-actions branch

Many names, TODO items, and other cleanup work needs to be done after the merge of "reorganize-actions"

blockly might make a nice UI... maybe even beyond developers.

It could make a pretty tangible representation of rspace.

Plus, the pieces are composable.

some stuff should go in localStorage too; e.g. a recent peek of the mailbox

I asked: what's the API for picking the right validator to deploy to? my mainnet deploys are SOOOOOO SLOOOOWWWW.

will said: https://status.rchain.coop/api/validators this is only for mainnet. The nextToPropose is the node you want to deploy.

hm. even after a deploy is done and the results are available at the deployId, the registry lags. Is this a finalization thing?

will: The default exploratory deploy which you are using for looking up data in deployId is using last finalized block to do that. You can use https://developer.rchain.coop/rnode-api#/rhovm/postExplore-deploy-by-block-hash-body to explore your data in the latest block

Why not just put each community into the rchain registry?

As long as we're in the dev tool space, for a somewhat chat-like UI, how about just using the browser console?

This would let us compose expressions, save values in variables, etc.

The agoric REPL does this trick where promises are sort of animated... they look like [promise 1] until they're resolved, and then pop! we see the {size: 10, color: "blue"} resolution. I don't think that's feasible with the console, but thingP.then(answer => console.log("got answer:", answer) might be kinda tolerable.

here's hoping I find time to review from this angle.

https://github.com/dckc/awesome-ocap/wiki/PetNames

p.s. This is meant as an issue in the liquid democracy work. @jimscarver , your latest work on directory.rho seems to be here in rho-bot, so I'm raising the issue here.

IOU a copy of my klunky Makefile, but I'd rather not inflict it on any / many more devs.

See also:

https://github.com/rchain-community/rchain-docker-shard

@tgrospic adds:

in client js example is also compose file (with bonds and wallets) for local testing.
https://github.com/tgrospic/rnode-client-js#run-rnode-with-docker