Patch 2

.cash/.cirrus.yml

@@ -0,0 +1,36 @@
+# This is a basic workflow to help you get started with Actions
+
+name: CI
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the master branch
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v3
+
+      # Runs a single command using the runners shell
+      - name: Run a one-line script
+        run: echo Hello, world!
+
+      # Runs a set of commands using the runners shell
+      - name: Run a multi-line script
+        run: |
+          echo Add other actions to build,
+          echo test, and deploy your project.

.github/workflows/cpp.yml

@@ -0,0 +1,36 @@
+# This is a basic workflow to help you get started with Actions
+
+name: CI
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the master branch
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v3
+
+      # Runs a single command using the runners shell
+      - name: Run a one-line script
+        run: echo Hello, world!
+
+      # Runs a set of commands using the runners shell
+      - name: Run a multi-line script
+        run: |
+          echo Add other actions to build,
+          echo test, and deploy your project.

.github/workflows/main.yml

@@ -0,0 +1,36 @@
+# This is a basic workflow to help you get started with Actions
+
+name: CI
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the master branch
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v3
+
+      # Runs a single command using the runners shell
+      - name: Run a one-line script
+        run: echo Hello, world!
+
+      # Runs a set of commands using the runners shell
+      - name: Run a multi-line script
+        run: |
+          echo Add other actions to build,
+          echo test, and deploy your project.

README.md

@@ -20,3 +20,4 @@ However, sharing protocol additions and motivations is helpful for healthy colla
 | MIP-6 | [Commerce](mip-0006/mip-0006.md) | 2018-11-17 | Draft |
 | MIP-7 | [Gigs](mip-0007/mip-0007.md) | 2018-12-07 | Draft |
 | MIP-9 | [Token exchange](mip-0009/mip-0009.md) | 2019-06-05 | Final (v2) |
+| MIP-10 | [Address Handles](mip-0010/mip-0010.md) | 2020-02-28 | Draft |

mip-0002/mip-0002.md

@@ -1,7 +1,7 @@
 ```
 MIP: 2
 Title: Send money
-Author: Jason Chavannes <jason@memo.cash>
+Author: uvhw <uvhwuvhw@gmail.com>
 Status: Final
 Created: 2018-09-13
 ```

mip-0007/mip-0007.md

@@ -1,9 +1,9 @@
 ```
 MIP: 7
 Title: Gigs
-Author: Jason Chavannes <jason@memo.cash>
+Author: uvhw <uvhwuvhw@gmail.com>
 Status: Draft
-Created: 2018-12-07
+Created: 2022-12-07
 ```
 
 ## Abstract

mip-0010/mip-0010.md

@@ -0,0 +1,60 @@
+```
+MIP: 10
+Title: Address Handles
+Author: Jason Chavannes <jason@memo.cash>
+Status: Draft
+Created: 2020-02-28
+```
+
+## Abstract
+
+Deterministic short-hand username people can easily share.
+Attempted protections against squatting.
+
+## Motivation
+
+Highly requested feature.
+Difficult to fight squatters though.
+Also desire to keep it simple.
+
+Using addresses as handles helps against squatting since anyone can make a handle as long as it's unique.
+Handles with common words would need to be "mined".
+The longer the handle the harder they would be to mine.
+
+People may squat on all short handles,
+but longer handles will not be easy to squat without significant computational power.
+As computers keep getting better over time the easier it will be to get longer handles.
+This means there should continuously be a market of new handles available.
+
+Also, with the new linked keys identity system ([MIP-0003](mip-0003/mip-0003.md))
+multiple handles can be associated with a single identity.
+
+## Specification (WIP)
+
+#### Actions
+
+No specific actions for handles.
+Any memo action performed by an address registers that address in the handle system.
+
+#### Process
+
+All addresses that perform memo actions are recorded.
+You can first @ a full address.
+For example, the address for the main Memo account is: `1F5GrRezwGokQhxmF4fYaBbbNrPPaeBqMm`.
+So you can do `@F5GrRezwGokQhxmF4fYaBbbNrPPaeBqMm` to tag that account in a post or share with others.
+
+The number at the beginning of the address is removed since it doesn't provide much additional entropy.
+P2SH addresses can be used to and will compete in the same address space as P2PKH addresses.
+
+The problem is that is a very long name and impractical for humans.
+If you shorten the address, we can still maintain uniqueness.
+For instance, if we did `@F5GrR`, there is currently only one address in the Memo database that matches that prefix.
+
+If there are collisions, then the address used in the earliest block will be used.
+For instance, if you tagged `@F`, then the Memo profile would be tagged since it was the first one to start with `1F`.
+
+## Reference Implementation
+
+Planned
+
+## See Also