Skip to content

Attempted rewrite of opening sentence #44

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

Open
JoshOrndorff wants to merge 2 commits into
base: rsign-ext
Choose a base branch
from
Open

Attempted rewrite of opening sentence #44

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a0292ca
Update rsign-ext.md
JoshOrndorff Oct 9, 2018
285cc41
Described why signatures are necessary.
JoshOrndorff Oct 9, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions pages/2018/rsign-ext.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,17 @@ date: 2018-10-08
published: false
---

I've been having fun in the RChain community working on smart contracts,
and we got past "hello world" to the point where incoming data needs to
be signed for the application to make any sense. And since I have a little
experience [building WebExtensions][ext], I put one together to make signatures
that Rholang contracts can verify.

The RChain ecosystem has been developing nicely the past few months. I've had fun writing smart contracts, as well as tools that make writing smart contracts nicer. With "hello world" and [other simple contracts][nth] in the rear-view mirror, we've reached the point where data need to be signed by users. Why do data need to be signed? Because without signatures anyone on the internet could cast votes, post statuses, or spend REV tokens on my behalf.

In the world of rholang, we facilitate object capabilities by using unforgeable names. These names exist only on the blockchain, and cannot be saved to disk or locked in a safe in the real world. Public-key crypto to the rescue. The user can lock their unforgeable name into "safe" a contract that anyone can call. When called the safe will give back the correct unforgeable name only if it is given a valid cryptographic signature

Since I have a little experience [building WebExtensions][ext], I put one together to make signatures that Rholang contracts can verify. If you've heard of metamask in the ethereum ecosystem, RSign may look familiar.

![RSign screenshot](https://github.com/dckc/RSign/raw/master/docs/screenshots/enterjson.png)

[ext]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions
[nth]: https://github.com/JoshOrndorff/nth-caller-game

[rsign-0.4.0.crx](https://github.com/dckc/RSign/releases/download/0.4.0-alpha/rsign-0.4.0.crx)
is an alpha release (Sep 21 2ddc1d5). Using Chrome or Chromium on linux, in developer mode,
Expand Down