Based on what you hear from forced cannonfodder recruits in Ukraine you won't have sufficient ammunition to do any real damage anyways because it's no longer about your people winning but to prolong the war money printer. 😔

Church of the flying mushroom Anunaki

Where are my crazy flat-earthers of Nostr??

I'm making a follow pack - reveal yourselves below, or tag who you know is 👇

be careful with signing stuff - you'll be in the bundeswehr in no time

we need to register Roganism as an official religion. 😂

Which sci-fi book is so good you wish you could read it again for the first time?

## Timekeeping via Bitcoin Blocks

### Core Concept

Replace Gregorian time with **block height + intra-block offset**:

```

[Block Height]:[Seconds Since Block]

```

- **Block Height**: Sequential blockchain position (e.g., `841,234`)

- **Seconds Since Block**: Elapsed seconds since block creation (0-599)

> Example: `841234:283` = 283 seconds after Bitcoin block 841,234 was mined

# Schema

```python

def gregorian_to_btc_time(gregorian_timestamp):

genesis_block_time = 1231006505 # Bitcoin's genesis (Jan 3, 2009)

elapsed_seconds = gregorian_timestamp - genesis_block_time

block_height = elapsed_seconds // 600 # 600s = 10min block target

intra_block = elapsed_seconds % 600

return f"{block_height}:{intra_block}"

```

- **Block Clock Sync**: Nodes sync time via block headers

- **Intra-Block Precision**: Sub-minute timing handled by:

- Network propagation averages

- NTP fallback for non-critical applications

- **Epoch Anchor**: Time `0:0` = Bitcoin genesis block (2009-01-03)

Schedule transactions using **OP_CHECKLOCKTIMEVERIFY**:

```bash

# Lock payment until block 850,000 + 90s

OP_IF

OP_CHECKLOCKTIMEVERIFY 850000:90

OP_ENDIF

```

| Feature | Bitcoin Time | Gregorian |

|------------------|-----------------------|--------------------|

| **Decentralization** | Consensus-based | Government-controlled |

| **Immutability** | Cryptographically secured | Politically mutable |

| **Censorship Res** | Permissionless verification | Centralized trust |

| **Global Sync** | Blockchain-native | Timezone complexity |

### Challenges & Mitigations

1. **Block Time Variance**

- *Issue*: Actual block intervals vary (2-120 mins)

- *Solution*: Use **block height** for long-term scheduling, seconds for short-term

2. **Time Resolution**

- *Issue*: 10-minute granularity

- *Solution*: Layer-2 solutions (e.g., Lightning Network timelocks)

3. **Ecosystem Adoption**

- *Path*: Wallet integration of BTC time displays

- *Tooling*: Block explorers with dual-timestamping

- **Smart Contracts**: Trustless expiration dates

- **Document Notarization**:

```markdown

Document #XZ42F timestamped at 841234:283

[SHA-256: a1b2c3...]

```

- **Scientific Records**: Tamper-proof research logs

- **Legal Agreements**: Unforgeable effective dates

> "Time is the only true decentralized commodity.

> Bitcoin didn't just create digital gold – it birthed a new clock."

> — Adapted from Andreas Antonopoulos

```

Gregorian: 2025-07-04 14:30 UTC

↓ Convert

Bitcoin Time: 841234:283 (Block 841,234 + 4m43s)

```

This system creates an apolitical, auditable time standard anchored in Bitcoin's immutable ledger – transforming time itself into a public good.

Use as a reference

They hid it below the pasta!!!!

Dinner #foodstr 🍔

CC nostr:nprofile1qqspgz966pym4w9r3wtkqad0leqncdfph0h0vtxyec6422vlf9cl9jsppemhxue69uhkummn9ekx7mp0casezl

True, in fact the only reason English managed to escape Dunkirk was due to the heavy resistance fighters of France and the English Commonwealth (Indians and others) that fought in the streets while it gave time for the English to escape.

Another huge story completely left out in movies like Dunkirk for example.

Now why leave out the valiant efforts of the French resistance and the Commonwealth soldiers? In fact the movie promoted the ships and vessels who came from England to save them, but not the men who died in the streets trying to slow down the Nazi advance to give the English time to flee.