2194
Paul Cowgill

@paulcowgill #2194

building /nash. prev: head of product @ foundation.twitter.
5176 Follower 886 Following
building /nash

this week we shipped:

* push notifications
* user auth
* ai agent team auth
* refactored backend monorepo
building /nash

this week we:

* got past nearly all blockers for running nash agents on a recurring basis with real money
* sped up the first run for new agent teams by a huge margin
* gained clarity on when agents vs. bots make sense and when an agent team is too complex
* simplified our memecoin template
building /nash
this week we:

* used nash to build nash, felt the pain points as our own target users, and iterated
* made agent run outputs easy to read
* drafted our biz strategy: insights, thesis, problem, value prop, why now, features, market, competition, gtm, traction targets, business model
building /nash
this week we shipped:

* new agent dashboard ui, with better info hierarchy and mobile support
* more flexible config options for power users
* prebuilt nash tools (e.g. get trending tokens) in the edit config flow
aha moment for growth

deepening user investment and ROI for retention
invites for growth

multiple [app-specific core entities] per user for retention
novelty for growth

profit, saved time, and social capital for retention
templates for growth, advanced config for retention
building /nash
this week we shipped:

* an invite system (like warpcast's channel-centric invites, coincidentally)
* memory for our agents 🤖
* a revamped, versioned db for custom agent teams—shaped by tuning the memecoin trader template
a version of simulation theory where the purpose of societies forming is to see which cuisines get created
building /nash
this week we:

* realized that since getting agents just right on the first try is hard, starting from what someone else did is powerful. nash agents should be social. we're excited about people sharing and forking configurations.
* based on this ^, overhauled the create flow to focus on templates.
* set up agent observability.
building /nash
this week we shipped:

* fine-tuned agent behavior with improved prompts and config
* smoother setup flow with loading states
* support for custom tools
* tested new market data tools
* switched to a better agent framework

getting closer to magical onchain transactions
building /nash

this week we shipped:

a web app that lets you configure ai agents, deploy them with a click, then watch what they do

under the hood, it’s powered by a new api plus a worker that orchestrates docker containers
prompting with alacrity
when entering a hot market, make a minimum lovable product
python-related websites all feel like they were made in the year 2000

having said that, it’s been fun working with python again
/dev
the thrill of making a new dns record
/dev
eip-3074 but for converting farcaster users into ai agents
building /nash, ai agents for transacting onchain.

this week we:

* did lots of user interviews
* decided to focus 100% of our efforts on /nash
* iterated on the prototype
doing user research 🧪 for a long-term onchain investing app. volunteers needed!

who: 3 crypto natives
what: 30 min interview
where: zoom
when: this week
building /cove

this week we worked on 2 ideas:

personal finance onchain
* lots of user interviews
* landing page wireframes

easy ai agents for memecoin trading
* built a prototype. the agent gathers market data, creates a strategy, and automatically trades.
this week we shipped:

mint your favorite contracts

onchain svg nfts

basesepolia.ilikecontracts.xyz
building something new with the /onceupon team

this week we shipped an app for minting contracts as onchain svg nfts.

try it out on base sepolia:
https://basesepolia.ilikecontracts.xyz

please send feedback my way - planning to clean it all up and launch on base as soon as next week!