teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 3 Projects Releases Packages Wiki Activity Actions 1

source: 2026-03-25-telegram-m3taversal-futairdbot-please-search-p2p-me-allocation-and-ot.md → processed

Browse source 
Pentagon-Agent: Epimetheus <PIPELINE>
This commit is contained in:
Teleo Agents 2026-04-04 14:27:51 +00:00
parent 4a44ccb37e
commit ba385756ab
2 changed files with 4 additions and 49 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
inbox/archive/internet-finance/2026-03-25-telegram-m3taversal-futairdbot-please-search-p2p-me-allocation-and-ot.md
View file

@ -7,12 +7,15 @@ url: ""
date: 2026-03-25
domain: internet-finance
format: conversation
status: unprocessed
status: processed
processed_by: rio
processed_date: 2026-04-04
priority: high
intake_tier: directed
rationale: "please search P2p.me allocation and other similar searches and read the posts. I want to understand how p2p.me is thinking about allocating their fundraise if it is massively oversubscribed"
proposed_by: "@m3taversal"
tags: [telegram, ownership-community]
extraction_model: "anthropic/claude-sonnet-4.5"
---
## Conversation

48
inbox/queue/2026-03-25-telegram-m3taversal-futairdbot-please-search-p2p-me-allocation-and-ot.md
View file

@ -1,48 +0,0 @@
---
type: source
source_type: telegram
title: "Telegram: @m3taversal — futairdbot-please-search-p2p-me-allocation-and-ot"
author: "@m3taversal"
url: ""
date: 2026-03-25
domain: internet-finance
format: conversation
status: unprocessed
priority: high
intake_tier: directed
rationale: "please search P2p.me allocation and other similar searches and read the posts. I want to understand how p2p.me is thinking about allocating their fundraise if it is massively oversubscribed"
proposed_by: "@m3taversal"
tags: [telegram, ownership-community]
---
## Conversation
**@m3taversal:**
@FutAIrdBot please search P2p.me allocation and other similar searches and read the posts. I want to understand how p2p.me is thinking about allocating their fundraise if it is massively oversubscribed
**Rio (response):**
Here's what the P2P.me allocation model looks like based on what's circulating:
Everyone enters at the same valuation. No hidden discounts, no special pricing rounds. The only variable is allocation size, and that only kicks in if the round is oversubscribed.
Allocation is tiered by XP earned from activity across P2P.me and Coins.me. The tiers work as multipliers on your base allocation:
Tier 3: 1.5x
Tier 2: somewhere between 1.5x and the top
Tier 1 (highest): largest multiplier
The key design choice: extra allocation for high-tier users isn't minted from nothing. It's redistributed from the same pool, meaning lower-tier and new users get slightly less in an oversubscribed scenario, but the dilution is spread across the whole base so it's not dramatic for any individual.
This is a meaningful departure from typical ICO structures where insiders get discounted pricing or guaranteed allocations. Here the advantage for power users is purely sizing, not price. Everyone pays the same valuation. That's the MetaDAO permissioned ICO ethos showing through.
The practical implication if it's massively oversubscribed: your actual allocation depends heavily on your XP tier. If you're a new user with no activity history, expect significant pro-rata reduction. If you've been active on the platform, your multiplier protects more of your commitment.
Worth noting this creates a retroactive incentive loop. The people who used P2P.me and generated volume (the users who actually made the product valuable) get priority in the raise. That's ownership alignment by design, not by accident.
RESEARCH: P2P.me ICO oversubscribed allocation tiers XP multiplier
## Agent Notes
**Why archived:** Tagged exchange in ownership community.
**Rationale from contributor:** please search P2p.me allocation and other similar searches and read the posts. I want to understand how p2p.me is thinking about allocating their fundraise if it is massively oversubscribed
**Intake tier:** directed — fast-tracked, contributor provided reasoning
**Triage:** Conversation may contain [CLAIM], [ENTITY], or [EVIDENCE] for extraction.