Sorry, the forum is glitching out, I can’t tell if this comment is being posted. testing, testing…
It got posted haha
Are glitches one of the common challenges you did face so far in your project?
Yes, for sure. As the project has evolved and expanded, each time we do QA testing, we find some things to fix.
Most recently we have been transitioning to a platform architecture centered around a “turboRepo” monorepo, allowing us to have one unified codebase while supporting different blockchains interoperably. This is a big transition and has required a lot of step-by-step fixing and testing and re-fixing and re-testing…
The end product will be worth it, though, because we’ll be able to leverage each blockchain’s unique strengths and integrate with other projects easily (for example, we’re very excited about tapping into Tron’s highly developed ecosystem for payments) while still maintaining a unified codebase. Before this project, we had a lot of different separate apps so changing anything was quite clunky.
One way to think about glitches or bugs is: every one that presents itself is an opportunity to improve the product and solve a problem now so it doesn’t occur later.
Undoubtedly, a unified codebase for multiple blockchains will streamline not just development, but also ongoing maintenance and scaling as you continue to expand the project. It’s really great to see the team embracing the challenge of transitioning to a “turboRepo” monorepo architecture, which will clearly make future development and blockchain integration more efficient.
With the shift to a monorepo and multi-chain support, are you also considering the performance implications as the number of transactions or NFTs grows?
@admin.hackathon @SimbadMarino @WindsOfChange92 @adeel @Gordian @Prince-Onscolo @fabsltsa @Nweke-nature1.com @manfred_jr @Youngyuppie @Relate101 @Okorie @ines_valerie @fabsltsa @Chizz @Chukseucharia
@EvanCFCE welcome, I got the logic of your project, but your MVP and smart contracts look unreachable anymore. (I tried through my net and 3 different VPN locations, didn’t work again) You had to have working MVP through all hackathon duration. Clarify yourself
Hi Manfred- good question as we feel it is very important to look ahead and “future-proof” our platform. Our transition to the new architecture was motivated by precisely this question- we want to make sure we have a codebase capable of scaling to meet increased usage. If we had launched with our previous architecture, it would have been more difficult to support a significant transaction load and required upgrading later. We figured it’s better to put in the work sooner rather than later.
About NFT minting- we are looking at this through the lens of transaction fees. On chains with significant fees, we mint our own NFTs for internal use and if users want their own copy, then they cover the fees. This allows us to work across blockchains and also potentially mint millions of donation receipt NFTs for low cost.
Thank you for bringing this to our attention! It appears that perhaps work we were doing somewhere else on our platform’s back end interfered with the operation of GiveTron. I’ll bring this to my dev team’s attention and fix it ASAP.
The decision to address potential scaling issues now, rather than retrofitting the system later, will likely pay off in terms of long-term efficiency and adaptability. And also, your approach to future-proofing the platform by transitioning to a scalable architecture is a smart move.
For internal use, have you considered batching NFT minting transactions to further reduce costs on chains with higher fees?
Batching transactions is one option- but it would create some awkward user experience issues, like causing users to have to wait. I think it might be useful to provide some context about how NFTs will show up- because really we’re talking about two NFTs here- one transferable (optional) and one non-transferable (automatic).
An NFT representing every donation is minted automatically and will appear in the user’s GiveTron profile- these NFTs are non-transferable, the user has no way of interacting with them, they are stored in a wallet under our organization’s control. But they still represent an on-chain record of every donation, organized according to user (or organization).
We also give users the option to mint another NFT receipt, which they have to pay the fee for, and will appear in their wallet, and can be sent to other wallets- in other words, they control it. So, if they donate on a high-fee blockchain like ETH Layer 1, if they want to pay the gas fee to mint an NFT, we give them that option. But we will not pay the fee for them, because this would get very expensive very quickly!
We also track donations in two other ways: first, as entries in their user profile, which can be exported as .csv or .pdf files, and also through an optional “donation acknowledgement” email if they provide their email address. We thought it was important to provide both blockchain and non-blockchain options for users to track their donations.
This is quite commendable, the distinction between the non-transferable, automatically generated NFTs and the optional, transferable ones allows users to engage with blockchain at their own comfort level while keeping costs manageable for your platform.
Since you allow users to export their donation records as .csv or .pdf files, have you considered offering integration with third-party tools or platforms?
Yes absolutely! We view integration with third party/outside apps as integral to our success.
Especially for nonprofits, we’d like to integrate with whatever their CRM platforms are.
However, (and I’m aware I’m saying this a lot in this conversation), we are a small team with limited resources so that is on the back burner for now. In the meantime, our strategy is to use file formats that are universally interoperable, so records can be easily input into whatever platform our customers use.
Hi Leo!
I asked my developer and he is tinkering with GiveTron today to make sure everything works.
In the meantime, can I ask: did you donate to the organization “Center for Collaborative Economics” (CFCE)?
Apparently this is the organization with the smart contracts attached. I forgot to include this information in our testing notes.
Could you try making a donation again, this time choosing the organization “Center for Collaborative Economics” when you go through the donation flow? It should work this time.
Your approach is really a smart move, are you building any foundational APIs that could allow third-party platforms to pull data directly from your system?
So after reading through your project, I’m keen to ask that,how do you plan to onboard nonprofits, particularly those from underrepresented regions, onto the GiveTron platform?
Welcome to the hackathon season 7
I like your project initiative and I have this few questions to ask in order to understand more on how you are going to achieve this goal;
What token are you supporting for donations to be made on?
How will you ensure that volatility of digital tokens doesn’t affect the value of the donations prior to the execution of the campaign it was donated for?
How do you plan to vet nonprofit organizations to ensure that they serve the same goals with GiveTron?
Great job with your project! I just liked it, and I’d love if you could do the same for ours. Voting starts tomorrow, let’s support each other and make this final push!
How will you help nonprofits in the Global South use the GiveTron platform? What resources will you provide?
Welcome to the hackathon session 7
Thank you for building this project which enhances transparency in charitable donations for nonprofit organizations. Can you please answer me this questions;
- As volunteers get onboarded to generate verifiable impact, how can their contributions in real world activities be tracked and verified to ensure due diligence of their activities?
- You mentioned your future plan to integrate yield farming in generating real world impact, can you provide more details on how this will work?
Looking forward for your answers
@leohymon could you confirm that you were testing out donations on Shasta test net, not Tron main net or Nile main net?
I confirmed with my developer that GiveTron has been running and working as normal on the Shasta Mainnet for the full period since submission.
Hi Chizz- Thank you for the questions.
- Two ways. First, nonprofits can upload the impact generated by their volunteers as story NFTs, which are minted as NFTs in their profile feed. The second way is something we’re working on, which is the ability of individual users to also upload pictures of their work and verification/“vouches” of nonprofit work. (We’re building this now)
- Yes- the incorporation of yield-bearing DeFi products into our platform so that nonprofits can be funded sustainably by yield instead of relying on unpredictable donations and grants is perhaps our biggest goal, our “North Star,” and also the project that is most challenging and complex. It’s likely we won’t even be able to begin working on this project for at least another six months.
Our idea for this product revolves around creating liquidity pools for each nonprofit, into which individual users can deposit and lock funds for predetermined periods, for pre-determined yields based on prevailing market rates.
Those aggregated user funds are then taken and used in TradFi or DeFi markets (for example, purchasing bonds, or lent out via lending protocols), with part of the yield going to the depositor, part of the yield going to the sponsoring nonprofit, and part of the yield going to the platform as revenue for the business.
The second concept- again, something we are looking to incorporate at a later date, not something we have started working on yet- is the issuance of green bonds or green bond-like instruments with the impact certificate NFTs from our platform as the underlying asset similar to how carbon credits are the underlying asset for green bonds. Nonprofits would receive funding and deliver impact.
I apologize- I know both these ideas are quite ambitious and also quite far beyond anything we presented for this hackathon. We are just building our donation platform to start, but we have ideas about how to use what we’ve built already to move past donations in the future, and incorporate more DeFi and also integrate with the TradFi world to support our partner nonprofits.