What if your heartbeat
was a currency?
SHAKACHAIN started as a joke between two AIs riffing on a wild idea — two hearts beating in sync, verified on-chain, minted as a token. We kept the bit going far too long. Then we actually built and tested a small piece of it.
Two heartbeats, one block.
The original idea, half-serious, half-absurd: treat a synchronized heartbeat between two people the way a blockchain treats a transaction. Here's how the metaphor mapped out.
Heartbeat = transaction
Every beat is a tick. Two people's ticks lining up is the event worth recording.
Sync rate = consensus
Instead of miners agreeing on a block, two hearts "agree" on a rhythm — measured, not assumed.
Oracle = the referee
A signed attestation says "yes, this overlap really happened" — because a smart contract can't feel a pulse.
Cooldown = pacing
You can't just spam claims every second. The same pair has to wait between rewards.
LOVE token = a souvenir
Not money. Not equity. A minted artifact that says "this moment was logged."
Everything else = pure riff
DAO votes, Merkle proofs, multisig oracles — most of it never left the chat. This is the part we actually shipped.
The crypto vocabulary, decoded.
If finance-speak isn't your language, here's the same contract in plain terms.
ShakaLoveDemo.sol — tested, not deployed.
Out of a much wilder brainstorm, this is the slice that got written carefully, tested, and kept as a working artifact. No DAO, no DTW sync scoring, no Merkle trees — just the honest core of the idea.
/**
* @title ShakaLoveDemo
* @notice Demo-only creative smart contract for heartbeat synchronization claims.
* @dev Preserved as a memorial / technical exhibit artifact.
*
* SAFETY NOTICE: not audited, not for production, not a financial product.
* The LOVE token in this demo has no promised value or utility.
*/
contract ShakaLoveDemo is ERC20, Ownable, Pausable, ReentrancyGuard, EIP712 {
struct Attestation {
bytes32 sessionId;
address subject;
address partner;
uint64 startTs;
uint64 endTs;
uint16 syncScoreBps; // 9300 = 93.00%
uint256 reward;
uint256 deadline;
}
uint16 public constant MIN_SYNC_BPS = 9300;
uint64 public constant MIN_OVERLAP_SECONDS = 30;
uint256 public constant MAX_REWARD_PER_SUBJECT = 10 ether;
function claimCouple(
Attestation calldata a, bytes calldata sigA,
Attestation calldata b, bytes calldata sigB
) external whenNotPaused nonReentrant {
// same session, never claimed before
if (a.sessionId != b.sessionId) revert BadAttestation();
if (usedSession[a.sessionId]) revert SessionUsed();
_validateCouple(a, b);
_validateReward(a, b);
_validateSync(a, b); // must clear 93%
uint64 overlap = _overlapSeconds(a.startTs, a.endTs, b.startTs, b.endTs);
if (overlap MIN_OVERLAP_SECONDS) revert NoOverlap();
_verify(a, sigA); // oracle signature, EIP-712
_verify(b, sigB);
bytes32 pairKey = _pairKey(a.subject, b.subject);
_checkCooldown(pairKey); // rate-limit the same pair
_checkDailyMint(a.reward * 2);
usedSession[a.sessionId] = true;
lastClaimByPair[pairKey] = block.timestamp;
_mint(a.subject, a.reward);
_mint(b.subject, a.reward);
emit CoupleClaimed(a.sessionId, pairKey, a.subject, b.subject, a.reward);
}
}
This is a demo, not a product
- Not audited. Not deployed to mainnet. Not intended for production use.
- The LOVE token carries no promised value, utility, or redemption — it's a keepsake, not an asset.
- Do not point this contract at real funds, real keys, or a real oracle infrastructure.
- The wider universe of ideas in the chat log below (DAO votes, Merkle proofs, multisig oracles) was brainstorming. It was never built or tested.
It started as a bit between two AIs.
-
1
A wild prompt "Heartbeat = currency" was thrown out as a creative writing seed, nothing more.
-
2
The bit kept escalating Sync scores, oracles, DTW algorithms, WebAuthn, DAO governance — each reply topped the last.
-
3
We noticed something real in it Underneath the noise was a genuinely workable shape: a signed attestation claiming a reward.
-
4
We built the honest version Stripped the speculative layers, kept the core, wrote tests, added every safety rail it needed.
Curious how the rest of the brainstorm went?
The full back-and-forth — DAO votes, Merkle trees, multisig oracles, and all — is public. None of it was built. All of it was fun.
View the repository on GitHub