# POLICAPS: Political Capital Tokens
**Technical Specification & User Guide**
Version 1.6 | January 2026
Dan Loewen | Senatai Cooperative
-----
## EXECUTIVE SUMMARY
Policaps (Political Capital tokens) are the core governance mechanism and economic engine of the Senatai Cooperative. They are designed to transform political engagement from an abstract “voice” into a quantifiable, auditable, and economically valuable asset that is inherently non-plutocratic.
**Policaps are:
- **Earned** through engagement with the predictive survey interface (with diminishing daily rewards)
- **Non-transferable** between ordinary users (hard defense against vote buying)
- **Spendable** on legislation to authenticate your position against predictions
- **Delegable** to trusted experts, increasing their spending capacity based on unique delegators (liquid democracy layer)
- **Cryptographically verifiable** with hardware-anchored integrity (tamper-proof voting records)
Policaps provide a verifiable, equalized form of political capital ensuring influence is earned through thoughtful civic labor, not bought with wealth.
-----
## 1. WHAT IS A POLICAP?
### The Data Structure
Each Policap is a cryptographic token containing:
```
Policap = {
bill_id: [Unique identifier for legislation]
law_id: [Unique identifier for laws within bills]
jurisdiction_id: [Location where law is relevant]
senatair_id: [Encrypted user identifier, contains profile data including location preferences/verifications]
question_id_variant: [Which survey question this answers, which QM made it, what K.E. was used]
encrypted_answer: [User response, encrypted]
timestamp: [When you answered]
daily_reward_limit: [Answers 1-10 earn 1 Policap each; answers 11-100 earn diminishing rewards
(answer 11: 0.99, answer 12: 0.97... answer 99: 0.02, answer 100: 0.01);
answers 101+: 0.001] Refreshes at 23:59:59 midnight UTC each day
device_fingerprint: [Unique device signature]
"key_image": [Cryptographic proof of unique spend],
"ring_members": [List of 10-15 public keys used for mixing],
hash: [Cryptographic signature proving authenticity]
}
```import hashlib
import json
# 1. Gather the data
policap_data = {
"bill_id": "C-11",
"law_id": "Section_4",
"jurisdiction_id": "ON-TOR",
"senatair_id": "Encrypted_User_X",
"answer": "Strongly_Support",
"timestamp": "2026-01-30T15:00:00",
"device_fingerprint": "Lenovo_2014_XYZ"
}
# 2. Convert to a stable string (sort_keys ensures the order is ALWAYS the same)
data_string = json.dumps(policap_data, sort_keys=True).encode()
# 3. Create the hash (The "Seal")
final_hash = hashlib.sha256(data_string).hexdigest()
# 4. Final Policap for the Ledger
policap_to_save = policap_data
policap_to_save["hash"] = final_hash
print(policap_to_save)
**Think of it as:** A digital receipt proving “User X answered Question Y about Bill Z at Time T using Device W” without revealing who User X is or what they answered (unless they choose to authenticate their vote publicly).
### Key Properties
- **Privacy-Preserving:** Encrypted and anonymized to protect voter identity
- **Hardware-Anchored:** Device fingerprint prevents bot farming and verifies origin
- **Tamper-Proof:** Cryptographic hash ensures data integrity
- **Auditable:** Complete transaction history verifiable on the ledger
- **Non-Transferable:** Ordinary users cannot send Policaps to each other, preventing vote buying
"The Auditor's Promise." > "Every Policap contains the seeds of its own verification. By re-calculating the SHA-256 hash using the provided open-source Auditor Script, any citizen can mathematically prove that their specific civic labor has not been altered by the Cooperative, the State, or any third party."
-----
## 2. HOW POLICAPS ARE CREATED
### Earning Policaps (The Only Way to Get Them)
Policaps are earned by thoughtfully answering survey questions generated by our predictive modules and tailored to your profile. This earning process serves as a gentle provocation to engage with bills you haven’t yet reviewed, generating crucial lo-fi predictive data that is a massive improvement over no information.
**Earning Schedule (Diminishing Returns):**
|Answers Per Day|Policaps Earned Per Answer|Anti-Abuse Purpose |
|---------------|--------------------------|-----------------------------------------------------|
|1–10 |1.00 Policap |Full reward for focused daily civic labor |
|11–100 |0.99–0.01 Policap |Diminishing returns to prevent grinding |
|101+ |0.001 Policap |Receipts to document bot-like behavior |
The earning limit refreshes every 24 hours at midnight UTC.
**Future Expansion:** We may tokenize real-world civic contribution including:
- Voting in elections
- Attending town halls, rallies, civic events
- Documented communication to elected officials
### What You CANNOT Do
- ❌ **Buy Policaps with money**
- ❌ **Transfer Policaps to friends** (prevents vote buying)
- ❌ **Sell Policaps to others**
- ❌ **Earn Policaps without enriching our data streams**
-----
## 3. ACCOUNT STRUCTURE: WHO CAN HOLD POLICAPS?
### Anonymous & Guest Profiles
**Anonymous Profiles:**
- Generate Policaps as receipts of answers
- Cannot spend Policaps to audit predictions
- Cannot delegate Policaps to experts
- Have no identifiers except apparent IP address
- Cede Policaps immediately as soon as they’re generated—nothing kept in browser or on device
- Policaps go to bill null accounts when generated
**Guest Profiles:**
- Have username/password
- Can hold Policaps temporarily
- Generate Policaps as receipts of answers
- Cannot spend Policaps to audit predictions
- Cannot delegate Policaps to experts
- Cede Policaps to null accounts of the bills that were the source for them when browser cookies are deleted
### Senatair Profiles (Ordinary Users)
Every Senatai member has:
- **Spend Account:** Can spend earned Policaps on bills
- **NO Receive Account:** Cannot receive Policaps from others (primary defense against vote buying)
**Account Status:**
- **Active:** Regular use
- **Dormant:** After 1 year of inactivity
- **Abandoned:** After 18 months of inactivity
- Co-op sends at least two messages to email/mail address about accrued dividend shares
- After 2 calendar years from last activity:
- Encryption keys destroyed or donated to null accounts (per profile settings)
- Dividend funds: 80% → trust fund, 20% → operations
**Account on Leave:**
- Contact local coop staff to put account on leave
- Data not considered abandoned
- Dividends held and accrue until reactivation
- Requires 2FA or other verification to reactivate
**Inheritance/Will Provisions:**
- Senatairs can specify in profile settings how to distribute their last dividend share upon death/incapacity:
- To other Senatair(s) of their choice
- To charity or institution
- Back to operations or trust fund permanent capital
- Requires proof of death/incapacity as specified in will
### Expert Profiles (Trusted Delegates)
Experts are users who have demonstrated domain knowledge and opted into receiving delegated Policaps.
**Account Structure:**
- **Spend Account:** Same base as ordinary users
- **Conditional Receive Account:** Can accept delegations
**Spend Limit Structure (Meritocratic Influence):**
**The Paintball Analogy:**
Imagine every Senatair standing before a massive legislative canvas.
**The Ammunition (Policaps):** These are the paintballs you earn through civic labor (surveys). You can only fire what you’ve personally earned or what has been delegated to you if you’ve earned trust by:
- Volunteering your credentials or experience
- Giving up anonymity within a specific domain
- Making convincing arguments in the forums
**The Equipment (Spending Capacity):** Every regular Senatair is limited to two paintball markers. Regardless of how many paintballs you have, you can only make a mark between +2 (Strong Support) and -2 (Strong Opposition). This ensures no single person can drown out the room.
**The Expert: Force Multiplication through Trust**
An Expert Profile is a Senatair who has earned community trust in a specific domain. When other Senatairs delegate to them, they are “lending their equipment.”
**Lending the Markers (Capacity):** When you delegate to an expert, you hand them your two markers.
**The Multiplier:** If an expert has 5,000 delegators, they wield 10,002 markers (their own 2, plus 10,000 from the community). Their influence expands from a small spot to a massive, undeniable mark of ±10,002.
**The Ammunition Flow:** Delegators choose exactly how many “paintballs” (Policaps) to give the expert. You might give a local environmental expert 1 Policap to see how they handle a specific bill. If you like the result, you might “reload” them with 50 more for the next month.
**Accountability: No Masking the Shot**
This power comes with a price. While regular Senatairs are pseudonymous, Experts are fully attributed.
- **The “Splat” is Signed:** When an expert fires 10,000 paintballs, the entire network sees exactly who pulled the trigger (but not which delegators provided the ammo)
- **Recalling the Gear:** If an expert votes against community values, delegators can “take their markers back” instantly. The expert’s capacity shrinks back to 2, and they have explaining to do in the forums
- **The $1 Fee (Anti-Abuse):** Prevents someone from creating 10,000 “Ghost Guests” to lend markers to themselves. Every “Marker” represents a real, verified human who paid $1 to be there
- **Hardware Agnosticity:** Software nodes handle the math of 10,000 markers; the mobile app just shows a simple “Delegate” button
- **Role 13 (Academic Institution):** Academic clients can track the “Muzzle Velocity” of different experts—seeing whose influence grows and whose delegators pull back in real-time
**Spending Capacity Formula:**
```
Max Capacity = 2 + (Unique Delegators × 2)
```
**Ammunition Limit:** The total Policaps an expert holds (from delegations) determines how many times they can use their boosted capacity. If they hold 50 delegated Policaps and their spending capacity is 202, they can only spend up to 50 Policaps on a single bill. The total delegated balance acts as available ammunition for their boosted capacity.
**Public Transparency:**
Expert profiles display:
- **Trust Balance:** Total delegated Policaps
- **Number of Unique Delegators:** Source of their capacity
- **Revocation Rate:** Credibility signal
### Elected Officials Profiles
A subset of expert profiles with special characteristics:
- **Expert Domain:** Their jurisdiction
- **Posted Credentials:** Official marks of office, bestowed by the state, verified by staff moderators
- **Special Badges:** Displayed in consensus forums
- **Special Privileges:** Can post topic threads, lead discussions, pin comments, host AMAs in legislative incubator forums
- **Same Rules:** Abide by identical spending capacity and Policap generation as other experts
- **Public Vote Records:** Within their official jurisdiction
**End of Term:**
- Delegated Policaps in elected official account either:
- Revert to delegators without reputation impact, OR
- Go to null accounts of bills that generated them if delegator account no longer active
### Bill Receiver Accounts
Every bill has three permanent receiver accounts:
1. **Support Account:** Receives Policaps spent in support
1. **Oppose Account:** Receives Policaps spent in opposition
1. **Null Account:** Receives:
- Anonymous/abandoned Policaps generated by answering questions about this bill
- Policaps from guest accounts when browser cookies are purged
- Policaps with encryption keys sent to null when sessions end
When you authenticate your vote, your Policap moves to one of these accounts, becoming part of the immutable record.
-----
## 4. HOW POLICAPS ARE SPENT
### Ordinary Spending (Authenticating Your Vote)
You spend ±1 or ±2 Policaps to authenticate your position on a bill against the prediction module’s estimate.
**Spending Limits per Bill (The Anti-Plutocracy Cap):**
Ordinary users can spend up to ±2 Policaps per bill. This hard limit is the core mechanism preventing whales or wealthy interests from dominating any single issue.
### Expert Delegation (Optional Liquid Democracy)
If you trust an expert, you can delegate Policaps to them.
**Mechanism of Influence:**
Delegation increases the expert’s spending capacity on bills related to their domain. The expert’s vote carries the cumulative weight of their own spending power plus the spending power entrusted to them by the community.
**Key Constraints:**
- **Domain-Limited:** Delegation tied to specific policy areas
- **Instantly Revocable:** You can withdraw delegation anytime, immediately reducing the expert’s available balance and next capacity calculation
- **Transparent:** You can see how experts spend delegated Policaps
This creates a **meritocratic hierarchy without permanent power**. Experts earn influence through continuous community trust, not credentials or appointments.
-----
## 5. ACCUMULATED INFLUENCE & THE PROBLEM OF OSSIFICATION
Any system that endures will generate hierarchies. Political capital compounds. Reputation compounds. Institutions outlive individuals. Attention is uneven, and time horizons differ.
**Pretending otherwise does not prevent aristocracy—it merely drives it underground.**
Senatai does not attempt to eliminate influential actors. It attempts to **govern the lifecycle of influence**.
### Design Principles
Policaps make accumulated power **legible, risky, and revisable:**
- Large concentrations cannot be exercised invisibly or diffusely
- They must be spent in discrete, public commitments that expose judgment to audit
- Greater accumulation = greater reputational and strategic risk
**Crucially:** No accumulation of Policaps confers permanent authority. Influence persists only through continuous renewal via:
- Voluntary contribution
- Demonstrated judgment
- Public justification
**Political capital that ceases to earn trust must decay.**
This principle applies uniformly—to experts, institutions, public figures, and officials. Senatai recognizes that hierarchy is inevitable. What it rejects is **ossification:** the conversion of past legitimacy into unchallengeable permanence.
By designing political capital as something that must be **spent, exposed, and re-earned**, Senatai transforms aristocracy from a hidden failure mode into a managed, accountable feature of democratic life.
-----
## 6. USE CASES: HOW THIS WORKS IN PRACTICE
### Scenario 1: Basic User Voting
Alice (regular Senatai member) earns 15 Policaps. She reviews Bill C-123 and agrees with the prediction to OPPOSE it. She spends 1 Policap to authenticate. Her vote is recorded on the ledger, and her balance decreases to 14 Policaps.
### Scenario 2: Expert Delegation (Demonstrating Increased Capacity)
**Initial State:**
- Maria (Tax Policy Expert) has 10 of her own Policaps
- 0 unique delegators
- Max Spend Capacity: 2 + (0 × 2) = **2 Policaps**
**First Delegation:**
- Bob delegates 50 Policaps to Maria
- Delegated balance: 50
- Unique delegators: 1
- New Max Spend Capacity: 2 + (1 × 2) = **4 Policaps**
**Second Delegation:**
- Charlie delegates 5 Policaps to Maria
- Delegated balance: 55
- Unique delegators: 2
- New Max Spend Capacity: 2 + (2 × 2) = **6 Policaps**
**Spending Event:**
Maria reviews Bill C-456 (tax reform) and strongly supports it, spending 6 Policaps (her current max capacity).
- **Total Influence Recorded:** 6 Policaps as highly significant authenticated vote
- **Maria’s balance:** 10 (own) + 55 (delegated) - 6 (spent) = 59 Policaps remaining
- **Transparency:** Bob and Charlie can see “Maria spent 6 Policaps on C-456 (support) using the community’s delegated influence”
- **Revocation:** If Bob disagrees, he can instantly revoke his 50 delegated Policaps, immediately reducing Maria’s balance and future capacity
-----
## 7. TECHNICAL DEEP DIVE
### Spending Algorithm
```python
def spend_policap(user_id, bill_id, amount, direction):
"""
Spend Policaps to authenticate vote on a bill
"""
# Verify balance and direction...
# --- EXPERT SPENDING LOGIC ---
if is_expert(user_id) and is_domain_relevant(user_id, bill_id):
base_limit = 2
# Calculate influence multiplier based on unique delegators
unique_delegators = count_unique_delegators(user_id, bill_id)
# Max spend capacity: Base + (Number of Delegators * Base Limit)
max_capacity = base_limit + (unique_delegators * base_limit)
# Expert must have funds to use calculated capacity
available_balance = get_total_balance(user_id)
# Amount spent must be ≤ max capacity AND available balance
if abs(amount) > max_capacity:
return Error(f"Cannot exceed max capacity ({max_capacity} Policaps)")
if abs(amount) > available_balance:
return Error("Insufficient Policaps in balance to cover the spend")
# --- ORDINARY SPENDING LOGIC ---
elif abs(amount) > 2:
return Error("Cannot spend more than ±2 per bill")
# Create transaction, broadcast, record...
return Success("Vote authenticated")
```
-----
## 8. TECHNICAL INTEGRITY & HARDWARE
### On-Device Hashing
To ensure sovereignty, the final cryptographic hash of a Policap is generated on the user’s **local hardware** (e.g., 2014 Lenovo or Sovereign USB Key). This creates an immutable “receipt” before data is transmitted to any network node.
### Paper Survey Authentication
When a paper survey is scanned or photographed at home:
- The app “seals” the image with the **Device Fingerprint**
- Provides authentication layer for analog data
- Links physical checkmark to registered hardware
8.2 The Asynchronous Ring-Mixing Protocol
To ensure high-level privacy (Monero-style), Policaps are not broadcast directly from the device to the ledger. Instead, they pass through a Staging Area (typically hosted on a Local Hub Node or Software Node).
- Ring Formation: When a Senatair "spends" a Policap, the app selects 10–15 "decoy" public keys from the active member directory.
- The Signature: The device signs the transaction using its private key combined with the decoys. To an outside auditor, any one of the 11–16 members could have pulled the trigger.
- The Staging Buffer: To prevent "Timing Attacks" (where an observer sees a vote hit the server exactly when you click 'submit'), the Staging Area holds the vote for a randomized period (0–6 hours) before broadcasting it to the global ledger.
The Senatai Policap Auditor Script
Python
import hashlib
import json
import sys
def audit_policap(policap_file_path):
# 1. Load the Policap from the file
try:
with open(policap_file_path, 'r') as f:
policap = json.load(f)
except Exception as e:
return f"Error: Could not read file. {e}"
# 2. Extract the hash that was recorded on the ledger
recorded_hash = policap.get("hash")
# 3. Create a copy of the data WITHOUT the hash to re-calculate it
# (Because the hash wasn't part of the data when it was originally hashed!)
data_to_verify = {k: v for k, v in policap.items() if k != "hash"}
# 4. Standardize the format (identical to the Minting process)
# This is where sort_keys=True is vital for consistency
check_string = json.dumps(data_to_verify, sort_keys=True).encode()
# 5. Re-run the SHA-256 math
calculated_hash = hashlib.sha256(check_string).hexdigest()
# 6. Compare the results
if calculated_hash == recorded_hash:
return "✅ AUDIT PASSED: This Policap is authentic and untampered."
else:
return (f"❌ AUDIT FAILED: Data corruption or tampering detected!\n"
f"Recorded: {recorded_hash}\n"
f"Calculated: {calculated_hash}")
# This allows the user to run it from the terminal: python auditor.py my_vote.json
if __name__ == "__main__":
if len(sys.argv) > 1:
result = audit_policap(sys.argv[1])
print(result)
else:
print("Usage: python auditor.py <path_to_policap_json>")
8.3 The Double-Spend Firewall
Because the Ring Signature hides the voter's identity, a malicious actor might try to use the same Policap twice.
- The Solution: Every Ring Signature includes a Key Image.
- The Rule: The Ledger keeps a list of all used Key Images for each Bill. If a transaction arrives with a Key Image that has already been recorded, the Software Nodes reject it immediately.
- Result: The system knows "The person who owns Key Image X has voted," but it never knows "Key Image X belongs to Dan Loewen."
-----
## 9. ECONOMIC MODEL: WHY POLICAPS HAVE VALUE
### Proof of Civic Labor
Your Policaps represent your labor and contribution to the collective dataset. They function as:
- **Receipt** of your answer
- **Unit of account** when tabulating authenticated votes on bills
### The January 1 Dividend
**Audit Period:** Every December 31, the Co-op audits all Policaps generated and spent.
**Disbursal:** On January 1, **25% of annual data revenue** (contributions + market returns + other revenue streams, excluding $1 lifetime membership fees and trust fund builder card revenue) is disbursed to members as the **Patronage Refund Dividend** based on the dividend share schedule.
**Meritocratic Bonus:** Users who contribute high-quality metadata (e.g., bias ratings) or earn badges they can display in forums through consistent auditing receive a higher share of the dividend pool, as outlined in the dividend share schedule.
**Key Metrics:**
- Users answering >365 questions per year: Bonus share
- Top 20% of auditors (measured by Policaps spent to confirm/override predicted votes): Higher potential bonus dividend share
*Note: Phrasing will be refined to ensure compliance with all regulations and cooperative norms.*
**How This Makes Democracy Functional:** Your voice becomes infrastructure, generating the financial power to hold institutions accountable.
-----
Section 9.1 (Privacy Protection) - The Observer/Consensus Split
Add this to bridge the ring signatures with your location logic:
Privacy vs. Jurisdiction: For the Consensus Pool, the Ring Signature is formed using members only within that jurisdiction. This proves that the voter is a verified local resident without revealing which specific neighbor they are. For the Observer Pool, the ring can be global, providing maximum "smoke" for those expressing outside sentiment.
## 10. REGULATORY COMPLIANCE
Policaps are **Utility Tokens**, not financial securities.
**Key Distinctions:**
- Non-transferable between users
- No speculative market value
- Used exclusively for “Consumptive Civic Use” and Co-op governance
- January 1 payout is a standard **Cooperative Patronage Refund Dividend**, legally distinct from return on investment for a security
-----
**End of Document**