From 48c2222a96fa9bab05b43812e9055043f0e20efc Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Fri, 28 Jun 2024 23:53:54 -0400
Subject: [PATCH 1/4] [LIP-27] The Lens Algorithm Marketplace.md

---
 LIPs/[LIP-27].md     | 52 ++++++++++++++++++++++++++++
 LIPs/lip-template.md | 81 --------------------------------------------
 2 files changed, 52 insertions(+), 81 deletions(-)
 create mode 100644 LIPs/[LIP-27].md
 delete mode 100644 LIPs/lip-template.md

diff --git a/LIPs/[LIP-27].md b/LIPs/[LIP-27].md
new file mode 100644
index 0000000..02c8649
--- /dev/null
+++ b/LIPs/[LIP-27].md
@@ -0,0 +1,52 @@
+---
+title: <Introducing the Lens Algorithm Marketplace>
+description: <A marketplace where algorithms can be rented and bought by Lens Users>
+author: <@zkjew (citing @ethwarrior “0x05-0x263d-DA-2d8c260b”)>
+discussions-to: <Lens>
+status: Draft
+type: <Protocol/Lens Open Algorithm Standard>
+category: <Contracts> 
+created: <(2024-06-28)>
+requires: <LIP-26> 
+## Abstract
+
+<!--
+  The Lens Algorithm Marketplace enables users to monetize their feeds and allows third parties to sell curated feeds to users. LIP-26 proposes a primitive where users can bring their own algorithms to a client and switch between them. This primitive introduces a new category of marketable assets. Instead of clients extracting value from users with their own algorithms, users can now create and sell access to their own algorithms. The marketplace fosters competition among users, clients, and third-party organizations in curating content for mutual benefit rather than exploiting users.
+-->
+
+## Motivation
+
+<!--
+  This LIP aims to create a marketplace for User-Owned Algorithm Tokens (UOAs) in order to expand their distribution. In this marketplace, users can purchase or rent UOAs, earn from their own UOAs, or utilize UOAs curated by third parties. By introducing a free-market approach to content curation, users can potentially benefit from algorithms that currently exploit them in today's social media landscape.
+-->
+
+## Specification
+
+<!--
+  The Lens Algorithm Marketplace aims to support the sale or rental of algorithms while keeping their contents confidential utilizing encryption and zero-knowledge cryptography where necessary. It should enable users, clients, third parties, and AI agents mining data to buy, rent, or sell their User-Owned Algorithms (UOAs) on the blockchain. Transactions should be settled via smart contracts, eliminating the need for intermediaries. Essentially, it should serve as an open marketplace where any entity can engage in various forms of trade and curation. 
+
+-->
+
+## Rationale
+
+<!--
+  Simply put, the Lens Algorithm Marketplace aims to commoditize User-Owned Algorithm (UOA) feeds, akin to how blockchains have commoditized cryptocurrencies like BTC and ETH.
+-->
+
+TBD
+
+## Backwards Compatibility
+
+No backward compatibility issues found.
+
+## Security Considerations
+
+<!--
+  All LIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. For example, include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. LIP submissions missing the "Security Considerations" section will be rejected. An LIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.
+-->
+
+Needs discussion.
+
+## Copyright
+
+Copyright and related rights waived via CC0.
diff --git a/LIPs/lip-template.md b/LIPs/lip-template.md
deleted file mode 100644
index 37e0748..0000000
--- a/LIPs/lip-template.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: <The LIP title is a few words, not a complete sentence>
-description: <Description is one full (short) sentence>
-author: <a comma separated list of the author's or authors' name + GitHub username (in parenthesis), or name and email (in angle brackets).  Example, FirstName LastName (@GitHubUsername), FirstName LastName <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
-discussions-to: <URL>
-status: Draft
-type: <Protocol, Lens Metadata Standard, or Lens Open Algorithm Standard>
-category: <Contracts, API, SDK> # Only required for Protocol. Otherwise, remove this field.
-created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
-requires: <LIP number(s)> # Only required when you reference an LIP which is also dependent on this to work. Otherwise, remove this field.
----
-
-## Abstract
-
-<!--
-  The Abstract is a multi-sentence (short paragraph) technical summary. This should be a very terse and human-readable version of the specification section. Someone should be able to read only the abstract to get the gist of what this specification does.
-
-  TODO: Remove this comment before submitting
--->
-
-## Motivation
-
-<!--
-  This section is optional.
-
-  The motivation section should include a description of any nontrivial problems the LIP solves. It should not describe how the LIP solves those problems, unless it is not immediately obvious. It should not describe why the LIP should be made into a standard, unless it is not immediately obvious.
-
-  With a few exceptions, external links are not allowed. If you feel that a particular resource would demonstrate a compelling case for your LIP, then save it as a printer-friendly PDF, put it in the assets folder, and link to that copy.
-
-  TODO: Remove this comment before submitting
--->
-
-## Specification
-
-<!--
-  The Specification section should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Lens platforms
-  TODO: Remove this comment before submitting
--->
-
-## Rationale
-
-<!--
-  The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages.
-
-  The current placeholder is acceptable for a draft.
-
-  TODO: Remove this comment before submitting
--->
-
-TBD
-
-## Backwards Compatibility
-
-<!--
-
-  This section is optional.
-
-  All LIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The LIP must explain how the author proposes to deal with these incompatibilities. LIP submissions without a sufficient backwards compatibility treatise may be rejected outright.
-
-  The current placeholder is acceptable for a draft.
-
-  TODO: Remove this comment before submitting
--->
-
-No backward compatibility issues found.
-
-## Security Considerations
-
-<!--
-  All LIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. For example, include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. LIP submissions missing the "Security Considerations" section will be rejected. An LIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.
-
-  The current placeholder is acceptable for a draft.
-
-  TODO: Remove this comment before submitting
--->
-
-Needs discussion.
-
-## Copyright
-
-Copyright and related rights waived via CC0.

From 2a814b7c83ff560bfdc2091ee54e2a717344e47e Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Sat, 29 Jun 2024 00:48:56 -0400
Subject: [PATCH 2/4] Update [LIP-27].md

---
 LIPs/[LIP-27].md | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/LIPs/[LIP-27].md b/LIPs/[LIP-27].md
index 02c8649..04e36c6 100644
--- a/LIPs/[LIP-27].md
+++ b/LIPs/[LIP-27].md
@@ -33,18 +33,12 @@ requires: <LIP-26>
   Simply put, the Lens Algorithm Marketplace aims to commoditize User-Owned Algorithm (UOA) feeds, akin to how blockchains have commoditized cryptocurrencies like BTC and ETH.
 -->
 
-TBD
-
 ## Backwards Compatibility
 
 No backward compatibility issues found.
 
 ## Security Considerations
 
-<!--
-  All LIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. For example, include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. LIP submissions missing the "Security Considerations" section will be rejected. An LIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.
--->
-
 Needs discussion.
 
 ## Copyright

From bcf11ed72cbc32ad95093ba08477367e8b37a4df Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Sat, 29 Jun 2024 00:53:41 -0400
Subject: [PATCH 3/4] Update [LIP-27].md

---
 LIPs/[LIP-27].md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/LIPs/[LIP-27].md b/LIPs/[LIP-27].md
index 04e36c6..ded5461 100644
--- a/LIPs/[LIP-27].md
+++ b/LIPs/[LIP-27].md
@@ -2,7 +2,7 @@
 title: <Introducing the Lens Algorithm Marketplace>
 description: <A marketplace where algorithms can be rented and bought by Lens Users>
 author: <@zkjew (citing @ethwarrior “0x05-0x263d-DA-2d8c260b”)>
-discussions-to: <Lens>
+discussions-to: <(https://hey.xyz/posts/0xdd33-0x087e-DA-00b18a3a)>
 status: Draft
 type: <Protocol/Lens Open Algorithm Standard>
 category: <Contracts> 

From 2ecb90a8b2305b145c5653b0d9c5382909eb1ade Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Fri, 23 Aug 2024 20:16:00 -0400
Subject: [PATCH 4/4] [LIP-27].md

Updated rough draft
---
 LIPs/[LIP-27].md | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/LIPs/[LIP-27].md b/LIPs/[LIP-27].md
index ded5461..50eb7df 100644
--- a/LIPs/[LIP-27].md
+++ b/LIPs/[LIP-27].md
@@ -1,6 +1,6 @@
 ---
 title: <Introducing the Lens Algorithm Marketplace>
-description: <A marketplace where algorithms can be rented and bought by Lens Users>
+description: <A marketplace where content creation by algorithm runners can be rented and bought by Lens Users>
 author: <@zkjew (citing @ethwarrior “0x05-0x263d-DA-2d8c260b”)>
 discussions-to: <(https://hey.xyz/posts/0xdd33-0x087e-DA-00b18a3a)>
 status: Draft
@@ -10,28 +10,29 @@ created: <(2024-06-28)>
 requires: <LIP-26> 
 ## Abstract
 
-<!--
-  The Lens Algorithm Marketplace enables users to monetize their feeds and allows third parties to sell curated feeds to users. LIP-26 proposes a primitive where users can bring their own algorithms to a client and switch between them. This primitive introduces a new category of marketable assets. Instead of clients extracting value from users with their own algorithms, users can now create and sell access to their own algorithms. The marketplace fosters competition among users, clients, and third-party organizations in curating content for mutual benefit rather than exploiting users.
--->
+<
+  The Lens Algorithm Marketplace enables users to monetize their content and allows third parties to sell curated feeds to users. LIP-26 proposes a primitive where users can bring their own feeds to a client and switch between them. This primitive introduces a new category of marketable assets. Instead of clients extracting value from users with their own algorithms, users can now create and sell access to their own content to algorithm curators. The marketplace fosters competition among users, clients, and third-party organizations in curating content for mutual benefit rather than exploiting users.
+>
 
 ## Motivation
 
-<!--
-  This LIP aims to create a marketplace for User-Owned Algorithm Tokens (UOAs) in order to expand their distribution. In this marketplace, users can purchase or rent UOAs, earn from their own UOAs, or utilize UOAs curated by third parties. By introducing a free-market approach to content curation, users can potentially benefit from algorithms that currently exploit them in today's social media landscape.
--->
+<
+  This LIP aims to create a marketplace for User-Owned Fees Tokens (UOFs) to be built. In this marketplace, users can delegate an "agent" who based on data from the user fills their feed with desirable or profitable content proposed by 3rd party curators. This allows users to earn from their ownership of UOFs, or utilize distribution by third parties to other users, as well as control how their feed is generated. By introducing a free-market approach to content curation, users can potentially benefit from algorithms that currently exploit them in today's social media landscape.
+>
 
 ## Specification
 
-<!--
-  The Lens Algorithm Marketplace aims to support the sale or rental of algorithms while keeping their contents confidential utilizing encryption and zero-knowledge cryptography where necessary. It should enable users, clients, third parties, and AI agents mining data to buy, rent, or sell their User-Owned Algorithms (UOAs) on the blockchain. Transactions should be settled via smart contracts, eliminating the need for intermediaries. Essentially, it should serve as an open marketplace where any entity can engage in various forms of trade and curation. 
+<
+  The Lens Algorithm Marketplace aims to support the sale or rental of algorithm generation processes and content inclusion to UOFs. It should enable users, clients, third parties, and agents running algorithms to buy, rent, or sell their 
+content curation to User-Owned Feeds (UOFs) on the blockchain. Transactions should be settled via smart contracts, eliminating the need for intermediaries. Essentially, it should serve as an open marketplace where any entity can engage in various forms of trade and curation. 
 
--->
+>
 
 ## Rationale
 
-<!--
-  Simply put, the Lens Algorithm Marketplace aims to commoditize User-Owned Algorithm (UOA) feeds, akin to how blockchains have commoditized cryptocurrencies like BTC and ETH.
--->
+<
+  Simply put, the Lens Algorithm Marketplace aims to commoditize content curation for User-Owned Feeds (UOFs).
+>
 
 ## Backwards Compatibility