# Project Profile

- Project Name: SlipSnitch
- Preferred X Username: @SlipSnitchApp
- X Bio: Make every fee explain itself. Local transaction audits, cost comparisons and tiny-balance checklists. Your wallet stays yours.
- Token Name: SlipSnitch
- Token Ticker: SLIP
- Token Description: SlipSnitch turns transaction costs into readable receipts and practical habit checks. Planned SLIP credits would unlock saved audit presets and expanded receipt exports. Local tools remain free, with no token required. Project tax rates and allocations are undecided; no financial distributions are promised.

## Pre-launch Tweet 1

```text
Your transaction history has receipts. Your habits have a bill.

SlipSnitch follows the fees: Network, Platform, Other.
A local audit starts with one question: where did it all go?
```

![A vivid fee classification flow prints an audit receipt](pre-launch-1.png)

## Pre-launch Tweet 2

```text
Same fee. Fewer repeats.

SlipSnitch lets you adjust a demo month's action count and compare the cost estimate. Turn the frequency down. Watch the receipt change.
```

![A local scenario changes monthly actions from 24 to 12](pre-launch-2.png)

## Project Launch Tweet

Publication prerequisite: publish only after the production domain and local demo are verified. This is application launch copy; the token remains planned and unissued. Replace placeholders only after issuance details are authorized and verified.

```text
Meet SlipSnitch: classify transaction fees, compare monthly habits and export a local receipt.

Planned token: SlipSnitch $<ticker> for saved audit presets and expanded exports. No token required today.
CA: <ca>

https://www.slipsnitch.xyz/
```

![SlipSnitch application workflow and planned credit uses](project-launch.png)

## Follow-up Tweet 1

```text
Start small: add one example transaction, name the fee and pick its category.

SlipSnitch turns the row into part of your receipt. Try a swap first. What did you pay for?
```

![Manual transaction fields for a local example](follow-up-1.png)

## Follow-up Tweet 2

```text
One category is not the whole bill.

Sort your sample costs into Network, Platform and Other. Which label makes the biggest difference to how you read the receipt?
```

![Separate fee category bars](follow-up-2.png)

## Follow-up Tweet 3

```text
A demo fee of $1.20 repeated 24 times is $28.80. Repeated 12 times, it is $14.40.

Change your monthly count in SlipSnitch. Compare scenarios before changing a real habit.
```

![Illustrative monthly costs at two action frequencies](follow-up-3.png)

## Follow-up Tweet 4

```text
Tiny balance. Not always a tiny recovery cost.

Use the checklist: inspect the balance, compare the fee, review the decision. SlipSnitch helps you write the plan; it does not move the assets.
```

![A three-step small-balance review checklist](follow-up-4.png)

## Follow-up Tweet 5

```text
The audit should leave with you.

Export a text receipt or print a copy from SlipSnitch. Keep the useful fields, and share a sample with private details removed. What would your receipt teach someone?
```

![Text and print receipt export workflow](follow-up-5.png)

## Follow-up Tweet 6

```text
A better comparison changes one thing at a time.

Keep the per-action fee steady. Adjust the monthly count. Read the difference. Try it with a local example before entering your own numbers.
```

![Controlled comparison holds fee steady while changing monthly count](follow-up-6.png)

## Follow-up Tweet 7

```text
A receipt should answer questions, not create them.

Which fee label felt unclear? Which export field would help? Share one suggestion for SlipSnitch, without private transaction details.
```

![Three concrete prompts for application feedback](follow-up-7.png)
