build strategy · onchain
Real onchain, five secrets, one build.
Every mega-prompt in this repo uses the same pattern, because it's the only pattern that lets a Lovable account ship a verifiable Cronos demo in one shot.
Why Cronos Testnet and not mainnet?
Cronos Testnet is a real EVM testnet — the same Solidity, the same explorer UI, the same wallets — but funded by a free faucet (test CRO). Every contract you deploy is publicly inspectable, but you never spend real CRO and your demo can't accidentally drain a user. Move to Cronos mainnet (chain 25) after the hackathon by swapping the RPC and chain id.
The recipe
recipe
# 1. In your Lovable project, add secrets (Settings -> Secrets): METAMASK_PRIVATE_KEY=0x... PRIVY_APP_ID=... PINATA_JWT=eyJhbGciOi... CRONOS_RPC_URL=https://evm-t3.cronos.com # 2. Fund the MetaMask deployer account with test CRO: open https://faucet.cronos.com/ # 3. Copy a mega-prompt from this repo into Lovable. One paste: # - scaffolds the React app # - writes the Solidity contract (with hackathon credit in NatSpec) # - deploys to Cronos Testnet and verifies on Cronos Explorer # - wires Privy social login (embedded wallet, user pays sub-cent gas) # - pins generated assets to IPFS via Pinata # - exposes the contract address + Cronos Explorer link in the UI # 4. Open the live Cronos Explorer link. Your demo is provably onchain.
1. The contract — credit baked in
Every Solidity file deployed from a Creative Blockchain prompt MUST carry the hackathon credit in NatSpec, so provenance lives onchain alongside the bytecode.
contracts/Provenance.sol
// contracts/Provenance.sol — every contract carries the hackathon credit in NatSpec
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;
/// @title Provenance
/// @notice Built during the Creative AI & Quantum Hackathon
/// @notice organised by StreetKode Fam during Indian Krump Festival 14
contract Provenance {
event Logged(address indexed author, string cid, uint256 at);
function log(string calldata cid) external {
emit Logged(msg.sender, cid, block.timestamp);
}
}
2. Deploy + verify on Cronos Explorer
scripts/deploy.ts
// scripts/deploy.ts — reads METAMASK_PRIVATE_KEY + CRONOS_RPC_URL from process.env
import { ethers, run } from "hardhat";
async function main() {
const F = await ethers.getContractFactory("Provenance");
const c = await F.deploy();
await c.waitForDeployment();
const addr = await c.getAddress();
console.log("deployed:", addr);
// verify on Cronos Explorer
await run("verify:verify", { address: addr, constructorArguments: [] });
}
main();
3. Pin assets to IPFS via Pinata
src/lib/pinata.ts
// src/lib/pinata.ts — pin a Blob to IPFS via Pinata JWT
export async function pinToIPFS(file: Blob, name = "artifact") {
const fd = new FormData();
fd.append("file", file, name);
const r = await fetch("https://api.pinata.cloud/pinning/pinFileToIPFS", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.PINATA_JWT}` },
body: fd,
});
const { IpfsHash } = await r.json();
return IpfsHash as string; // the CID
}
4. Sign in with Google via Privy
src/main.tsx
// src/main.tsx — Privy social login (embedded wallet, user pays sub-cent gas)
import { PrivyProvider } from "@privy-io/react-auth";
import { cronosTestnet } from "viem/chains";
<PrivyProvider
appId={import.meta.env.VITE_PRIVY_APP_ID}
config={{
loginMethods: ["google", "email"],
embeddedWallets: { createOnLogin: "users-without-wallets" },
defaultChain: cronosTestnet,
supportedChains: [cronosTestnet],
}}
>
<App />
</PrivyProvider>
Hackathon rules of thumb
- · One mega-prompt = one build message. Don't iterate the architecture, iterate the UI.
- · Always show the live Cronos Explorer link in the UI — that's your proof.
- · Have judges grab free test CRO from faucet.cronos.com — gas is sub-cent on Cronos.
- · Pin every user-generated asset to IPFS the moment it's created.
- · Add a "Built during the Creative AI & Quantum Hackathon — StreetKode Fam · Indian Krump Festival 14" line to your footer.