baymac

Short version: journal runs got the full durability stack, which is a state machine in SQLite, an operation ledger, leases, a reconciler and a drainer. Chat reused the ledger and idempotency layers but deliberately left out leases and resume, because a chat turn is short enough that recovering one means asking again.

Architecture (journal runs)

Everything durable lives in ensol.db, a single SQLite connection whose writes are serialised by a promise-chain mutex (database.ts). The layers:

1. Run state machine. Each run is a row in agent_runs with a phase, a version and a driver lease. Moving to a new phase is a compare-and-set on version, so if two writers race, only one wins.
2. Command ledger. acceptCommand / loadCommandByIdempotency (repositories/commands.ts). Every client command carries an idempotency keyd. A retry replaysthe stored result; the same key with a different payload
   raises a confli
3. Provider operation ledger. Each model call gets a

baymac

➜  keystone3-firmware git:(master) ✗ python3 build.py -o simulator > error.log
warning: patch for `bitcoin` uses the features mechanism. default-features and features will not take effect because the patch dependency does not support this mechanism
warning: skipping duplicate package `embedded` found at `/Users/parichay/.cargo/git/checkouts/rust-bitcoin-c060ecb653881637/f4fc5be/bitcoin/embedded`
warning: unreachable pattern
  --> /Users/parichay/minswap/keystone3-firmware/rust/keystore/src/algorithms/rsa/mod.rs:75:9
   |
75 |         _ => Err(KeystoreError::RSASignError),
   |         ^
   |
   = note: `#[warn(unreachable_patterns)]` on by default

baymac

diff --git a/packages/sign-client/package.json b/packages/sign-client/package.json
index 9c61b52b..36c016af 100644
--- a/packages/sign-client/package.json
+++ b/packages/sign-client/package.json
@@ -24,7 +24,7 @@
     "build:source": "rollup --config rollup.config.js",
     "build": "npm run build:pre; npm run build:source; npm run build:types",
     "test:pre": "rm -rf ./test/tmp && mkdir ./test/tmp",
-    "test:run": "vitest run --dir test/sdk",
+    "test:run": "vitest run test/sdk/persistence.spec.ts",

baymac

## Set the Cardano Node Socket Path
export CARDANO_NODE_SOCKET_PATH=$(ps ax | grep -v grep | grep cardano-wallet | grep mainnet | sed -E 's/(.*)node-socket //')
 
## testing that it worked
echo $CARDANO_NODE_SOCKET_PATH
 
## Changing to the Documents folder and creating a folder
cd ~/
cd Documents
mkdir nami-submit

baymac

Keybase proof

I hereby claim:

• I am baymac on github.
• I am parichayb (https://keybase.io/parichayb) on keybase.
• I have a public key ASBIL2gtOIHVQfrWB_VZg4ODZMPwYsGlSvm74gCbKpmV2wo

To claim this, I am signing this object:

baymac

layer*[] split(network *net, LAYER_TYPE layer_type) {
  layer *split_layer = net->layers;
  int i = 0;
  while(layer_type != split_layer->type) {
    split_layer++;
    i++;
  }
  // a b c d e f
  // 0, 3
  return [0, i];

baymac

import { open } from "https://deno.land/x/opener/mod.ts";

const url_ = Deno.args[0];

await open(url_);

baymac

yarn run v1.19.1
$ yarn build && electron-builder build --publish never
$ concurrently "yarn build-main" "yarn build-renderer"
$ cross-env NODE_ENV=production node --trace-warnings -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.main.prod.js --colors
$ cross-env NODE_ENV=production node --trace-warnings -r babel-register ./node_modules/webpack/bin/webpack --config webpack.config.renderer.prod.js --colors
[1] Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade caniuse-lite browserslist`
[0] Hash: b0ace21e23866de7d874
[0] Version: webpack 4.16.3
[0] Time: 6681ms
[0] Built at: 11/09/2019 10:16:30 PM

baymac

cmake_minimum_required(VERSION 3.14)
project(mnemonics C)

set(CMAKE_C_STANDARD 11)

add_executable(mnemonics main.c wordlist.h)

baymac

Application period & Before

What did work well?

I started interacting on the community gsoc-sig gitter channel from May 3rd. It was nice and cordial response from the org admins and mentors. That really helped to be motivated and have confidence. We had frequent meet ups on hangouts. Everything was very professionally managed.

What should we improve?

I only think to improve the participants count and project ideas. We can embrace new tech stacks. The millennials are more inclined towards newer programming languages like Python, JS, Kotlin etc. This is also important for Jenkins to keep up with the pace. To take advantages of all the developments.