tweak the meeting notes a bit

stellar-deprecated · Feb 16, 2024 · a8d03a2 · a8d03a2
1 parent 64ab687
commit a8d03a2
Show file tree

Hide file tree

Showing 6 changed files with 35 additions and 113 deletions.
diff --git a/docs/notes.mdx b/docs/notes.mdx
diff --git a/meeting-notes/2024-01-18-protocol-dev.mdx → meeting-notes/2024-01-18.mdx b/meeting-notes/2024-01-18-protocol-dev.mdx → meeting-notes/2024-01-18.mdx
@@ -1,7 +1,7 @@
 ---
-title: 'Protocol & Developers Call'
+title: '2024-01-18'
 authors: naman
-tags: [protocol, developer]
+tags: [protocol]
 ---
 
 <audio controls>
@@ -29,4 +29,4 @@ tags: [protocol, developer]
 1. What are the best practices for managing transactions in the frontend, with respect to transaction ordering.
 1. Core devs confirmed that ordering is intentionally arbitrary.
 1. Request for an API for current version of the environment/sdk
-1. Github issue filed for the RPC to return versions of the current node.
+1. Github issue filed for the RPC to return versions of the current node.
diff --git a/meeting-notes/2024-01-26-dev-meeting.mdx → meeting-notes/2024-01-26.mdx b/meeting-notes/2024-01-26-dev-meeting.mdx → meeting-notes/2024-01-26.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Developer Meeting'
+title: '2024-01-26'
 authors: kalepail
 tags: [developer]
 ---
@@ -30,4 +30,4 @@ tags: [developer]
    1. Observe create contract ops as ledgers close
    2. Use an [indexing service](https://soroban.stellar.org/docs/reference/data-providers#data-indexers)
 6. What is the status of contracts caching support? - [question](https://discord.com/channels/897514728459468821/1199121845656486009/1200484710447587490)
-   1. [response](https://discord.com/channels/897514728459468821/1199121845656486009/1200516877680644276)
+   1. [response](https://discord.com/channels/897514728459468821/1199121845656486009/1200516877680644276)
diff --git a/meeting-notes/2024-02-01.mdx b/meeting-notes/2024-02-01.mdx
@@ -0,0 +1,27 @@
+---
+title: '2024-02-01'
+authors: naman
+tags: [protocol]
+---
+
+<audio controls>
+  <source
+    src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Stellar-Protocol-Meeting-02-01-2024.mp3"
+    type="audio/mpeg"
+  ></source>
+  Your browser does not support the audio element.
+</audio>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1201979721211203614)
+
+1. The proposal is to advance stellar-core by adding a host function to verify the secp256r1 signature, which is the most common elliptic curve used outside of the blockchain space. It is useful in connecting off-chain authentication interfaces with on-chain functionality.
+1. Note that the proposal is not for a new signer type but a host function.
+1. Leigh investigated adding support for the WebAuthN use case, by allowing a custom account / smart contract to sign soroban auth entries using a secp256r1-signed payload.
+1. secp256r1 is supported by phones, passkeys, and enables an app to replace passwords. This is a massive benefit to user-facing applications like wallets.
+1. Pros and cons of the interface: blockchains generally implement the recovery interface over the verification interface but verification is easier for developers as it reduces burden on the client and the network.
+1. The WebAuthN use case requires encoding and decoding of base64 payloads and decoding JSON blobs, which is not currently supported in Soroban.
+1. While there are hacky ways of accomplishing the latter, it’s not a great developer experience and final implementation is susceptible to breakages on updates.
+1. It is also costly to bundle decoding with verification in guest.
+1. Soroban has always led with a batteries included mindset. Keeping in line with that approach, it makes sense to further investigate and determine whether a host function makes sense for these as well.
+1. Leigh’s implementation may require further evaluation of the crates used for ecdsa and p256.
+1. Brief discussion around proposed process for adding of a host function by a non-core dev.
diff --git a/meeting-notes/2024-02-09-dev-meeting.mdx → meeting-notes/2024-02-09.mdx b/meeting-notes/2024-02-09-dev-meeting.mdx → meeting-notes/2024-02-09.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Developer Meeting'
+title: '2024-02-09'
 authors: kalepail
 tags: [developer]
 ---
@@ -17,4 +17,4 @@ tags: [developer]
    1. [SEP draft](https://github.com/orbitlens/stellar-protocol/blob/sep-0042-token-lists/ecosystem/sep-0042.md)
    2. [Discord discussion](https://discord.com/channels/897514728459468821/1162558946867953704)
 2. Stellar + Soroban documentation survey
-   1. [Take the survey](https://discord.com/channels/897514728459468821/1204462856037470248/1205196745877757962)
+   1. [Take the survey](https://discord.com/channels/897514728459468821/1204462856037470248/1205196745877757962)
diff --git a/sidebars.js b/sidebars.js
@@ -6,7 +6,7 @@ module.exports = {
     },
     {
       type: 'link',
-      label: 'Meeting Notes (Blog Version)',
+      label: 'Meeting Notes',
       href: '/meetings',
     }
   ]