Summary
Technical Platform Issues Identified Initial discussions centered on critical technical blocks, including the requirement for a full KYC documentation redo due to the old platform and fi xing the BSL price discrepancy in the app which incorrectly displayed zero metrics. Legal Review for Token Allocation The team reached a consensus that legal review is necessary regarding the security risks of allocating tokens potentially derived from stolen funds, agreeing to hold such tokens until offi cial case closures to protect the DAO. Community Focus Exchange Strategy The strategy for exchange listings was decided to be a community-driven ‘fl ash mob’ mobilization targeting Tier 1 exchanges rather than pursuing lower-tier exchanges that demand large listing fees. Exchanges like Coinbase and Kraken require listing submissions, and require several of them. We have been approached by Coinbase to list before.
Details NEEDS FURTHER DISCUSSION
● SLP Marketing Fund Allocation Allocating funds from the SLP for growth opportunities. Must be further defi ned by determining key performance indicators, audience segmentation (general vs. targeted), and assessing the application’s readiness before a proposal is fi nalized and brought to a vote.
ALIGNED
● Coin Market Cap Access and Update Coin Market Cap (CMC) has been engaged to make necessary changes, and review the proposed token description.
● Bank Social App Price Display Fix Apple release pending (Android/Play store is available) to fi x the Bank Social app price display issue, where the main page percentage change is incorrectly showing 0%.
● Previous Meeting Minutes Approved The meeting minutes from the previous meeting are formally approved.
● Known Bugs List Implementation A known bugs list will be implemented, documented, and communicated to the community via the new portal, featuring links for bug submission and a general status page detailing current work.
● BSL Token Rewards Demo Preparation Work on the proposed BSL token allocation rewards experience will continue, aiming to have a demo available by the next session’s call, utilizing the delegate chat to refi ne the concept before bringing it to a governance vote.
● Legal Review of Fraudulent SLP Funds legal review will be performed regarding a legal opinion to return the BSL funds impacted by movement to the SLP wallet, specifi cally concerning tokens implicated in potential fraud, until their conclusion.
● Tier 1 Exchange Listing Campaign A community ‘fl ash mob’ action plan will be organized to contact Tier 1 exchanges (Coinbase, Kraken) weekly with listing requests, requiring Nate and Jeremy to start compiling a comprehensive list of contacts and forms by next week.
More details:
● Discussion of KYC Redo and Technical Blocks: Darlene Hilton informed Nathaniel O’Dell that Josh needs to redo all the Know Your Customer (KYC) documentation, which is currently on the old KYC platform and requires Phil to delete the existing information fi rst. Nathaniel O’Dell noted that Karan is also experiencing technical diffi culties, suggesting it may be a similar situation as the message was exchanged over Telegram .
● CoinMarketCap (CMC) Page Updates: Nathaniel O’Dell provided an update on the CMC page, noting that the contract address and the proper block explorer were updated, which the DAO was pleased about. The discussion confi rmed that the price is close to accurate, and the volume of $7,969 is now showing under bank social markets on the page, indicating the market is back online.
● Access to Self-Reporting Tools: John Wingate stated that they have access to a self-reporting tool for CoinMarketCap, which allows updates to be made through the interface rather than email, though updates still require review . John Wingate plans to meet with Nathaniel O’Dell for 15 minutes the following day to provide them with the necessary username and password to log in and make changes, as well as to review the proposed description update. The team also acknowledged that the CoinGecko page needs updating.
● Bank Social App Pricing Discrepancy: John Wingate requested that Jeremy Dube contact MD and Arturo to address the issue of the BSL price not working correctly in the bank social app. The problem is that the main page shows 0% for the percentage change, volume zero, and market cap zero, even though a percentage change is visible elsewhere in the app. It was suggested that this issue arose when Saucer Swap went down, leading to a temporary stop in using CoinMarketCap data.
● Jeremy Dube’s E-commerce Work: Jeremy Dube updated the team on their work setting up e-commerce, noting the challenges of setting up shipping to the US due to tariff s, which led them to pause US shipping and focus on Europe and France. They expressed enjoyment in using cloud services and customizing pages on Shopify for product descriptions and articles, fi nding success in creating detailed prompts for Claude .
● AI Planning Mode for Development: John Wingate advised Jeremy Dube on best practices for using AI tools like Claude for long-term tasks to avoid “hallucination,” which occurs when the context window fi lls up. The recommendation is to use “planning fi rst,” where time is spent creating a detailed plan with Claude that generates the most succinct contextualization for the fi rst new prompt . John Wingate explained that their team uses a base markdown fi le that outlines repository standards, and they create a feature branch and a plan for every new feature to ensure the AI can pick up from prior work seamlessly .
● Formal Meeting Approval: The meeting was called to order at 4:14, and a quorum was established with Michael Allen, Jeremy Dube, and Kranthi
Kalagara in attendance, along with Darlene Hilton, John Wingate, Nathaniel O’Dell, and Sara Khadar from Bank Social . The meeting minutes from the last session were formally approved by motion and second, with John Wingate confi rming that the motion carried .
● Standardized Bug Reporting Location: The team discussed the need for a standardized location to report bugs and issues, confi rming that tickets can be submitted through the support portal . To improve the process, the team agreed to utilize the delegate and verifi ed chats for prioritizing submitted tickets, with John Wingate committing to working with Kevin to create a documented “known bugs list” that will be communicated to the community and published on the new portal.
● Multi-IG Development Status: John Wingate reported that multi-IG development has not progressed signifi cantly due to the time commitment required for conference preparation. This task remains on the roadmap but is currently a lower priority than cleaning up voting-related issues, which needs to be completed before launching the new DAO portal .
● BSL Token Allocation for Rewards: The topic of BSL token allocation and movement of set DBSL to the SLP wallet was discussed, specifi cally addressing Michael Allen’s request to sort out the incentive rewards for Credit Union (CU) members . John Wingate reported that the front end for the rewards experience is already under development, and the team will plan for a demo to be available by the next session’s call. The immediate task is for the delegates to propose an idea of what the rewards should look like, which will be integrated with screenshots for the governance discussion .
● Security Concerns Regarding Stolen Funds: A signifi cant discussion focused on the security and legal implications of allocating tokens that may be derived from stolen funds, with John Wingate emphasizing the risks of scammers making false claims . The consensus reached was that for the DAO’s protection, it is necessary to avoid taking discretion on individual cases, to wait for offi cial case closures before action is taken, and potentially to seek legal review on the matter of the contract execution being fi nal. John Wingate committed to discussing the matter with corporate counsel to determine if getting a formal opinion is worthwhile, or if the tokens should just be held until a fi nal conclusion is reached.
● Strategy for Token Listing on Exchanges: The discussion shifted to token listing on exchanges, noting that large exchanges like Binance, Coinbase, and Kraken do not require listing fees but look for community interest and volume
. John Wingate discouraged pursuing lower-tier exchanges that require large upfront fees and often result in fake volume, stating they would not vote to use SLP funds for such listings. The most benefi cial approach was determined to be a community “fl ash mob” strategy where hundreds of people send emails to tier-one exchanges (e.g., Coinbase, Binance, Kraken) to request a listing.
● Developing the Exchange Listing Mob Strategy: The delegates were tasked with compiling a list of target exchanges and contacts for the community mobilization eff ort. John Wingate confi rmed they would provide the Coinbase contact and form, and Jeremy Dube volunteered to take responsibility for Kraken contacts and information. The plan is to reference this community mobilization eff ort in the following day’s chat and distribute the fi nalized list to the verifi ed chat the following week.
● Allocating Funds for Marketing: Jeremy Dube raised the idea of allocating funds from the SLP for marketing purposes, potentially hiring a marketing company like Ninja Promo, which John Wingate has worked with previously . Sara Khadar noted that the company has historically used organic marketing, and this would be a shift to paid media. Sara Khadar emphasized that before launching any paid media campaigns, the application and entire ecosystem must be ready for a general audience to ensure a “stellar” fi rst impression.
● Marketing Strategy and Target Audience: The team agreed that paid media is necessary to reach beyond the current maximum community saturation, suggesting that targeted marketing to people who care about self-custody would be more eff ective than a general audience campaign. Sara Khadar plans to follow up with a questionnaire to defi ne the target demographic and determine the key performance indicators (KPIs) for measuring success, with the aim of discussing specifi c routes and options at the next delegates meeting). Jeremy Dube’s initial idea was to use SLP funds to promote the wallet, including paid search on exchanges to improve ranking, making the BSL token more visible.
● Highlighting the DAO in the 100th Blog Street Issue: Sara Khadar requested that delegates provide a quote or blurb by the end of the following day for a dedicated section in the 100th issue of Blog Street, which will highlight the DAO and its delegates. Jeremy Dube had already sent a list of suggestions that Sara Khadar plans to incorporate.