Before upload, check if the checksum is the same and block the user if that the same

[riderx]

This is made to stop mistakes We could also propose to user when upload to build for them

[riderx]

/bounty 30

[algora-pbc[bot]]

💎 $30 bounty • Capgo

Steps to solve:

1. Start working: Comment /attempt #309 with your implementation plan
2. Submit work: Create a pull request including /claim #309 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Additional notes:

ℹ️ If something is not clear ask before working on it, otherwise your chance to rework it is high 🎥 To claim you need to provide in your PR a demo video of the change 👨‍👩‍👧‍👦 Join the Discord to get help 📏 Check all Bounty rules

Thank you for contributing to Cap-go/CLI!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @asr2003	Jul 5, 2024, 4:34:30 AM	#310
🟢 @hunxjunedo	Jul 5, 2024, 3:53:43 PM	WIP

[richardokonicha]

/attempt https://github.com/Cap-go/CLI/issues/309

[algora-pbc[bot]]

💡 @asr2003 submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[asr2003]

/attempt #309

Algora profile	Completed bounties	Tech	Active attempts	Options
@asr2003	1 bounty from 1 project	JavaScript, Go, HTML & more		Cancel attempt

[hunxjunedo]

@riderx from my understanding, what we are trying to achieve is that whenever a user trying to upload directly, we need first compare the upload's checksum to last uploads checksum to remove any chances of uploading the same thing twice. Is that true ?

[hunxjunedo]

/attempt #309

Algora profile	Completed bounties	Tech	Active attempts	Options
@hunxjunedo	1 bounty from 1 project	JavaScript		Cancel attempt

[algora-pbc[bot]]

[!NOTE] The user @asr2003 is already attempting to complete issue #309 and claim the bounty. We recommend checking in on @asr2003's progress, and potentially collaborating, before starting a new solution.