SHIPYARD / OPS

Event Stub

Meetup hosts check people in and attendees keep a stub that remembers who they met there.

At a Lagos builder meetup, guests scan in at the door and tap phones to connect with people they meet. Weeks later, Femi opens his stub and sees the three people he promised to follow up with.

Built for

The jobs it does

Rally a communityOwn my identity and reputation
Blueprint

How the vessel is built

Mission

Make the people you meet in a room as easy to remember and reach as the talks you saw.

The need

Meetups are where people find collaborators, jobs and co-founders, but most connections are lost by Monday. Hosts only see headcount, and guests leave with half-remembered first names.

What it will never do

  • Add someone to your stub without your tap
  • Show the host who met whom by name
  • Put names, notes or contacts onchain
  • Message people on your behalf
Owner playbook

Pick your voyage

Event Stub lets meetup hosts check people in by QR, gives each attendee a stub that remembers who they met, and nudges follow ups weeks later. On a ticketing platform, the platform owns your attendee list and the connections made in your room. Own it, and every check in, every stub and every 'who I met at your event' memory belongs to you as the host, deployed from your wallet.

Straight answers

Before you own it

Will attendees bother tapping phones?

Some will, especially at builder meetups. Make it part of the welcome: 'tap three people before the talk'.

Do attendees need crypto?

The stub should work with a simple sign in; wallets can come later. Test the flow with someone non technical before the event.

I can't code.

Check in QR, stubs, tap to connect, reminders and analytics come built.

What about privacy?

Connections are only shared between the two people who tapped. Hosts see counts, not who met whom.

Is it really mine?

Yes. Deployed from your wallet on Base, Celo or Polygon.

Same berth

Nearby vessels

The whole yard →