This guide helps users and developers migrate from the old TipStream contract to the new V2 deployment.
- Address: SP31PKQVQZVZCK3FM3NH67CGD6G1FMR17VQVS2W5T.tipstream
- Version: v1.0.0
- Address: SP1W6XQZ6XVYGTVW32SJW2ZG48ZJBW9BATRD19N60.tipstream
- Version: v2.0.0
- Deployment Block: 7940053
- All tipping functionality works identically
- Same 0.5% platform fee
- Same user interface
- Same wallet connection process
- Tips sent to the new contract start fresh (no history migration)
- User profiles need to be recreated
- Previous tips remain viewable on old contract
- No immediate action needed - frontend automatically uses new contract
- Optional: Recreate your profile on the new contract
- Optional: Export old tip history for records
Update your contract configuration:
// Old
export const CONTRACT_ADDRESS = 'SP31PKQVQZVZCK3FM3NH67CGD6G1FMR17VQVS2W5T';
// New
export const CONTRACT_ADDRESS = 'SP1W6XQZ6XVYGTVW32SJW2ZG48ZJBW9BATRD19N60';
export const CONTRACT_VERSION = 'v2.0.0';No breaking changes - All function signatures remain the same.
Test your integration:
# Update environment
VITE_CONTRACT_ADDRESS=SP1W6XQZ6XVYGTVW32SJW2ZG48ZJBW9BATRD19N60
# Run tests
npm test- Not automatically migrated
- Users can recreate profiles manually
- Consider building a migration tool if needed
- Old tips remain on old contract
- Query both contracts to show complete history
- Example:
const oldTips = await fetchTips('SP31PKQVQZVZCK3FM3NH67CGD6G1FMR17VQVS2W5T');
const newTips = await fetchTips('SP1W6XQZ6XVYGTVW32SJW2ZG48ZJBW9BATRD19N60');
const allTips = [...oldTips, ...newTips];If issues occur:
- Revert frontend to old contract address
- Users can continue using old contract
- Fix issues and redeploy
Questions? Check: