Community update from Powerhouse Ecosystem Actor | AVC SoFi | SEED Latam

Transcript

[Music] [Applause] [Music] [Music] [Music]

[Music] [Music] [Applause]

[Music] [Music] [Music] [Music] [Music]

[Music] [Music] [Music]

[Applause] [Music] [Music] [Music] [Music]

[Music] [Music] [Music] hi everyone welcome thank you for being here yes yes I'm about to yes that's why I'm about to introduce you guys thank you all for being here on time this is a very interest interesting

call regarding the latest updates um from Powerhouse so we have share the the link from the post because there are probably many questions that are going to address here today so while we are waiting it's important that you also type during the call all the questions that you may have for this meeting we have like a like an agenda to follow and you are going to listen this from from wter wter is a pleasure to have you here again welcome T we're going to have both of them from Powerhouse I don't know if

you guys are ready to start or if you want to um wait for more people to join but I think we're ready so whenever you want please go ahead yeah well actually we're I'm just going to make like a brief um introduction from both of you but if I'm aware that you also are a wter you're going to mention about the like the general work that you've been

doing here uh but I think that you might be the the right one for give us all an like an introduction hello everyone welcome and thanks for joining I'm not uh sure if we're supposed to wait a little bit longer as people are still joining yeah maybe I'm going to start just while we wait while we wait for yeah yeah uh do you want to mention the

agenda that you guys have shared with us while we wait for more people to join I suspect uh Chris may have some issues connecting the audio uh so I think I'll I'll kick us off so uh yeah again welcome everyone um thanks for so far oh apologies I cannot hear her yeah I hear

uh like the the jingles and everything but I can't hear any voices okay what about now I left the chat and I came back again are you can you hear me now I think the only one that can hear me it's everybody can hear me right can you please give me like a reaction so I know that everyone can hear me okay good this is Kanga I can hear you Chris Walter do you hear me same here I can hear

everyone you here okay this is totally normal we've been having issues with this for so long so okay well we're going to wait for wter to to come back and in just a while but yeah this is kind of like normal so I don't know if maybe T do want to start but the agenda basically that I'm going to also share with all of you so you can be aware um on the certain topics we have also shared these um in the Forum in our Discord channel so basically water is going to give like a general

introduction from like 20 minutes and then they're going to be like um some time for questions and then T is going to talk us and he has a presentation some slides some wi friends uh related to uh re assets and the post but H this is important we have been issues right with the transparency and communication so I think that these are the perfect meetings you know we have the guests here and there are a lot of questions and we sometimes do not have answers when we post the questions in the Forum and we you say it out loud so what's the best way to have the

guests in here to receive some answers and even if they don't have the answers well they must like um know and address the the questions that we may have so um yes have your questions ready you can share whenever you want during the call and I don't know if water you can hear me now is it here I cannot see in the call uh yes so can you hear me now water

all right can everyone hear me because I'm still unable to hear anything okay then um just tell me in the Channel that I can talk I'll walk us through the intro I have 10 calls every day but of course now the audio setup breaks all right um yeah so apologies for that I'll uh share my screen and then just get started okay so I'll walk us through

this um so yeah thanks for having us we uh were very excited to have uh the first of hopefully a whole series of community calls where we can talk more in detail about our um our road map and our role at makerd Dow um so yeah we are Powerhouse Powerhouse is involved in building and rolling out software that will implement the atlas rules in the form of the universal Dow toolkit uh if you've been following the Forum you may have seen that uh We've introduced oursel a while ago and um so there was a recent status update where we uh uh we uh talked a bit more about our role so we are building

the software for efficient decentralized operations transparency reporting and operational data management um we are helping Dows to conduct to conduct business process analysis so this is how they work internally and um T will talk a little bit more about how we go about this and how we are helping maker though uh specifically with real assets portfolio reporting but um as part of our role we also want to co-create with stakeholders so that's why we are here today uh talking about the features that we're building um to collect that early feedback make sure that we were building what's really

needed and in doing this we um enable maximum progress towards automation AI integration and participation in the Dow so the infrastructure that we're building that manages all this data it really makes the organization AI ready and of course with Maker's Vision around Atlas and the involvement of AI we think this is a very good match and then lastly we tie it up with decentralized operation solutions for pseudonymous contributors because this two um has been a challenge for many DS how to work effectively with pseudonymous contributors and build a longlasting working relationship with contributors and um yeah make sure that the da knows

who to trust and um how to work with them so that's quite a lot and uh so this is the reason why the stack that we're offering is um uh actually has a couple of different uh areas and layers and um I'm going to give this quick intro uh just to create a little bit of context um what uh the topic that t will be talking about where you can see that in the the yeah the many things that we're doing um so the way that it's structured is that in the first place we are building a decentralized operations based infrastructure here at the bottom so um

this is a suite of Open Source Products for maker that will be fully integrated with the atlas and um these are really the the tools to build um what we call business features on top of and these business features uh they they are quite specific to the organization so while while the products that we're building are very general uh they will be offered not just to maker D but also to other DS because that is part of the vision of endgame to build self- sustainable businesses um the business features that we're building they are uh on the contrary they're quite specific to the organization and so the business

features that we're building for maker they are different than the business features that we're building for other Dows for maker for example today we will be talking about reild assets portfolio reporting a specific feature from maker um there's uh other features that we're considering for the future road map things like the ecosystem actors directory uh AVC membership Administration uh transparency reporting tools tailored for makers use case and then also um venturing to Legal Tech uh which is part of the concerns that D contributors typically have to make sure that that is also uh custom built for for maker purposes there's other features like projects and road maps of

course there is a a general component to it um but the good the good thing is that we can tailor these features again uh exactly to the needs of the specific organization and that is thanks to the infrastructure layer that um that all these business features are built on top of the next thing is that um our uh infrastructure offers this um this functionality not just in a userfriendly way to human contributors but all these functionalities they are automatically because of the framework that we're using automatically uh they are available to um AI agents as well so um

if we build a feature for example the re asset portfolio reporting that will'll go into detail today um we show you typically the manual uh process the the manual editor which is needed for humans to interact with the feature but all these uh all the buttons all the uh all the sliders all the menus that you see they're um available for AI agents as well and that that makes us uh yeah really well suited to prepare the organization for further uh API Integrations um agent training facilitation for example uh AI agent integration and so on clearly this is a developing uh area of what we're doing

but um this is uh built in or baked into it from the start and then last but not least uh building software is is not enough for success in an organization um we need to make sure that the software is actually rolled out successfully and is properly adopted by everyone and so this is um the last uh part the last piece of the puzzle that we're offering is uh an important layer of Operational Support uh so as I mentioned we do things like business process design um but more in general like we we help think about decentralized or design uh we build the software that matches that but then we

do the software onboarding and adoption help with the adoption as well make sure that the different ecosystem actors are coordinated that contribute to the software um and then we also offer uh project management assistance because the uh the key to uh building successful decentralized operations for a d such as maker uh is to make sure that the organization can work effectively with uh with its ecosystem actors or its suppliers um and so yeah that's uh we we offer that that manual assistance as well because that is needed to turn the whole thing into success um as I mentioned we we have these different layers and so that means

that our our development uh timeline is uh is also reflecting that and that is something that is quite uh important to keep in mind when uh we're providing updates is that as Powerhouse is an entirely new uh spinoff uh and that we started I think about half a year ago along the the path that we're currently on um and so we need some time first to build that to put that base infrastructure in place and make sure that we are building we we have the basic tools that will allow us to uh build those business features that I was talking about on top of so for example um in the past uh months we've been

working uh with our team to start thinking about uh very general infrastructures such as document modeling that is the you know shaping the the data that is available the data and the processes in the organization uh how can we Define that for example with a schema language um how can we capture that and how can we uh provide document editors that will allow any contributor to um View and edit that data in the organization this is very general function ality and then we take those tools and use them to build those business features on top of for example re asset portfolio reporting and so

today um for the first time we'll dive deeper into one of those business features that typically as a customer uh the most out contributors will be most excited about because this is Major specific stuff but uh again thinking about our development stages keep in mind that uh uh we we need some time to build out that bu That Base infrastructure and then as we progress over time um we'll be able to build those business features uh in yeah in more and more rapid succession uh so re asset portfolio reporting is the first one uh but the pace will pick up and and more many more will uh follow in in the

coming year and then lastly of course we do need to make sure that there is that operational roll out make sure that it's not just the software that is available but also um that it is correctly adopted by the organization so that being said uh we do have uh since uh like since the short time ago we have enough uh of a view on our road map to um commit at least to a an MVP Alpha version release so this will be um a version first version of the software that will feature one of those uh business features specifically the one we're talking about today real portfolio reporting um and uh yeah we we will have

that first test version available for the community not to start using very heavily in production from day one but uh already to start trying it out uh provide more feedback and um yeah keep uh keep improving until we get to that uh that production quality that we want um that first Al Alpha version release in our case is actually It's a combination of two elements so one is the the new architecture MVP what I was talking about these these different layers with the base infrastructure the um the business feature built on top of that uh specifically providing that

functionality for real asset portfolio reporting but um for those of you who have been following us for a a bit longer you know that we have already built a number of prototypes in the past for maker um as we um we progressed from the makerd Dow sustainable ecosystem scaling core unit uh one point we realized we need to start building software to implement best practices uh in the the infrastructure of The Da rather than only talking about best practices and we built those prototypes and uh so for our first release um while these prototypes were uh separate from the new uh product Vision that we've developed around

Powerhouse uh we are not throwing those prototypes away on the contrary we are extending them and we are refactoring them uh so that that same functionality will be available uh in that mvp Alpha version release as well so we're combining that with the new features and uh yeah basically making use of the prototypes that were developed before to give you more specific ideas so um yeah I think a year and a half ago something like that we uh released the first uh prototype version of our expenses dashboard which brought at the time a lot more transparency to core unit expenses and so this is one example of a prototype that will be transitioned into

a longer term uh product and in this case uh this will become the PowerHouse Fusion platform which is the the public uh collaboration platform that uh that is part of our product Suite there's a second tool which is known to maybe the core unit administrators much more specific that is used by the core units to report those expenses or to publish the numbers to the platform the expenses dashboard and um yeah this this is a very early prototype of um the kind of editor software that we'll be looking at today um and yeah in the same way that we'll talk

about re asset uh portfolio reporting uh the core units have already been doing that reporting around their expenses with an early prototype budget tool as we called it and so that one um will be completely revised and uh provided with a much better user experience through the new connect product but again there is some continuity there so that we yeah we take our lessons learned and and transform that tool into the new version the decentralized identity and reputation solution Renown um for that one one we we don't have a prototype available that's used at maker today but um yeah we actually did the hackaton a while ago so if

you're um if you're really interested we can share with you um some uh some presentation that shows that one but this one is is mostly a new development that we're preparing for the alpha release as well and then um yeah as I mentioned we want to be AI ready make sure that all the functionality all the processes that we are implementing are available to AI agents as much as to humans so um we already started with that Vision pretty early uh with the expenses dasor API which is also available in a in a sandbox studio and that one too will be uh included in the new version and and reworked the last uh product is um typically one that people

are also excited about uh there an academy product uh we think that one will be absolutely critical in the future but right now this one isn't in active development and not included in the alpha release um yeah this is another overview of what I already mentioned so I'll skip over it and um with all that context in place uh want to be a little bit more specific so these different products that were building these different business features the features that we're building the alpha release that we're preparing for how does that all come together um well this is uh this is basically it in in one picture so for the alpha release we are

um working on four different tracks uh the first two protocol expense accounting and uh the Project based workflow uh this is the expanses dashboard and the existing prototype such as the API that we are reworking into the new products so that is included for the MVP Alpha release of course the these are the kind of features that are never really uh fully finished so um what we will be delivering is uh a integrated version of those uh first version that works on the new uh architecture if you're interested in the details you can have a look in the Forum post or um Join one of our future Community calls where we'll be talking

about them but today we are going to focus on uh the next one which is so the integrated reable asset reporting feature uh which uh contains so yeah it U it contains uh functionality on the public collaboration platform Fusion uh it will be available through the new API um but today I will talk about the uh specific reporting flow that people will be using in our connect product so that's that's the focus of today's discussion and then of course to support all that uh we will need uh that new base infrastructure so the power has proof of concept uh that has the four base products Fusion switchboard connect

and Renown uh working together and to support these these other features so this is what we will be talking about uh today and then um in the in the coming weeks as well with the additional Community updates but um for today I want to hand it over to tip who will be talking about what specific uh track on these Force so the integrated real assets reporting uh feature and um yeah I'll suggest that maybe tip uh or someone else can take over the screen sharing because it will be very complicated for me to uh go to the next slide if I don't hear uh anyone

asking so uh I'll stop my screen sharing here and hand it over to De well thanks fter um just check everyone can hear me yes [Music] perfect [Music] so so I'll basically pick up in the same presentation without a left off so basically now uh for this part of the call we will zoom in on the real asset reporting feature um and then also show

you some updated wireframes um and some early stage low fality designs um that we've basically worked on but first of all I wanted to take sort of um step out and talk about the PowerHouse business analysis flow so this is basically the flow that we will do uh when uh designing and um coming up with new features uh in the road map so we did this flow for real world asset reporting it'll be the same for projects um and any of the other new business features um that we have in the road map um so maybe starting off at the top for people that are unfamiliar with what

exactly business analysis is uh it's all about translating business needs into features that add value um so real world asset reporting for example noticed a lot of discussions over the past year on The Forum um in the community that um that reporting could be improved and we basically believe that we can provide a solution for that so business analysis uh our flow is then split into these steps um to make sure that we cover the full requirements so the first step that we do is problem statement and solution I'll drill into these a bit more um and then we go to a needs analysis we Define who's actually involved and who are the

stakeholders then we def Define some specific examples then we construct low Fidelity wireframes which is the step we're on now and then we hand over to designers which construct High Fidelity designs um which can then be handed off to our developers to actually create the feature that can be used uh in production so zooming in on the individual steps um the problem statement and solution is all about identifying a specific issue or Challenge and proposing a corresponding resolution so realwood assets for example we um we identified that the issue was that there was a lack of

unified and efficient reporting um and this was because there was no specific software there wasn't a framework that was uh followed it seemed to be different per different arrangers um and this resulted in some problems such as uh data fragmentation um it's also hard to compare results when they're not providing in the same format um so these type of things and then we identified a proposed solution so this solution we identified was um to create an automated reporting platform that integrates seamlessly with the workflows the important Point here is that we want to create a solution that doesn't require any extra work um by any of the parties involved but it but it

basically uh meets the needs of the problem and makes everyone's lives uh kind of better the next stage in the flow then would be a needs analysis and Gathering stakeholder requirements so we have the problem um and then we have to list through who are all the stakeholders so we actually group them down into who's responsible accountable consulted and who needs to be informed and then split them out into action and implementation so action stakeholders would be um people or parties that actually uh commit the action so in this example have real world assets the arranges um and the allocated D operators would be

the action stakeholders they will be the ones that use the uh infrastructure that we create and the implementation stakeholders are the ones that create that software or practices so we identified Powerhouse ba Labs uh as an example and then we reach out to all of the stakeholders that we identify and basically check their requirements and also check specific tasks so an arranger uh has a requirement that they want to report accurately on the transactions and their specific tasks is that they need to basically submit those transactions ledgers and reports um so once all of these requirements are collected we can then Define more specific user roles and

responsibilities so the main uh roles and responsibilities uh from the requirements is basically the arranger who is submitting the transactions to the operator with proof of correctness so they basically submitting evidence and transactions to the operator who acts as a sort of audit function uh that will then review these transactions um for correctness and completeness then the next step is to define specific use case scenarios so these are basically um very specific examples of how the software or the product or the feature will be used um so they need to be relatable um and they

need to be specific and they need to then capture the needs that we laid out in the earlier steps so for example use case one is all about opening up the uh application clicking to their profile uh clicking through their transactions and assigning them putting supporting evidence and then submitting that transaction uh report to the operator and we create a variety of these use case scenarios and these then basically go to inform low Fidelity wireframes so we um develop initial representations of basic structures and functionalities so this looks sort of familiar like software but it doesn't have the details of a high

fidelity final design and we then iteratively uh collect feedback from stakeholders to ensure that these um wireframes and Designs meet their needs um for the problem so that is the business uh analysis flow and now I will open up the wireframes and show you guys um in detail what we've come up with so this first screen here is an example of the connect application that vouter um mentioned earlier so this would be opened in a browser window or a application on the

users PC and they would be asked to log in with Renown so this is where they will tie the um ethereum address or decentralized identity to their actions within the application so they would authorize the application and then they would be logged in uh in the workspace here in the first example we will walk through uh it's from the view of an arranger so in this we have monus so monus is logged in and they're then presented with the uh drives that they have access to based on um what is relevant for them basically so they'd navigate to their team drive and they'd have a list of the transaction reports

um that are already been created and then they would be prompted to open the transaction report specifically with the real world asset portfolio editor so this is a specific document editor Just For Real asset um reports and it will only allow people to do specific functions relative to real world asset reporting they would click through there and open up this and this is the view that they would see when they entered into the report so if any of you have seen the RO asset reports on the Forum uh the inspiration for this uh has been brought from there so the they open it up they have a navigation bar they have the current date uh of the portfolio as

it was last updated or as it has been updated they could uh filter on SPV for this example we have taco and they would have um a table here with information on the current as well as sold and matured assets so they have ID and name maturity if it's relevant the notional value and the purchase price and the realized Surplus so this table view here is a condensed view of the data that's contained and the user could then uh click the individual asset and it would open this form at the bottom which has uh more detailed breakdown of the information so you can see there's

additional Fields such as qip qip and isin which are identifies for real assets as well as notional uh and the purchase price which is here as well as purchase proceeds which is additional information and this calculation at the bottom shows the total discount and the current value as well as if there's been any surplus that's realized uh as well as the total Surplus and then at the bottom here you can see when this asset was last updated and by who with the ethereum address and a date and this is the sort of condensed view but for each page that we will show show that's in portrait there will be in a company in landscape view which will have all the information from the from

the form at the bottom available within the table so you could see it in one go if you had a a wide monitor so from this view uh the user or the arranger may want to add or edit an asset so they could um they could edit asset details and this button here and it would take them through and it would only allow them to edit certain Fields as the other field are basically a function of the underlying transactions and what I mean by that is that the type and the maturity in the qip and the name are relevant to the asset but the transactions uh underneath it basically added up to inform these uh numbers at the bottom which I'll show uh in a

minute that also be an option similar similar form can you try and zoom in just a bit more I think um the details better visible for people yeah that's much better thank you yeah let me know if um if there's any more I'll try and zoom in a bit a small screen um this is the similar form but for adding an asset so same thing you would add the uh fields that are relevant but the other ones are calculated from the underlying transactions so when they had this page with all the assets that might be relevant they then want to go and see transactions um which is the lower level

sort of underlying information underneath the asset portfolio so they would navigate to this this tab and similar layout to the uh to the portfolio page you'd have this table at the top um with information such as time stamp uh the asset involved the quantity if it is relevant um some will not have a quantity if they things like interest the US the amount of the transaction and the corresponding cash balance change which is the change in the cash balance as a result of this as well as if there's any attachments that are linked to this transaction and how many uh there might be um so if we take this

example here the arranger selects transaction number three and this opens the form of the bottom the same way and this signifies that there's a group transaction and this is the group transaction view basically what I mean by that is this transaction 99 Zoom 96510 um is a group transaction which has multiple underlying base transactions so through our discussions with the stakeholders monist and Stakehouse um they basically told us that monist would like to submit um information on the lowest possible lever to make make it easier or the arrang so they

basically want to upload things like bank statements um and have all the transactions get submitted um this way but for the end users that want to conru like conduct some data analytics or um have an understanding of the portfolio and sometimes transactions actually need to be grouped so if we take this example here there's a purchase of uh 1 million T bills so that is the first transaction there's a million of the T bills that are moved to uh to this report and the resulting uh cost of this was 99643 but then there was additional two transactions um on top of this which is the sadon broker fee of $7 and an

exchange agent fee of $100 resulting in a total cash balance change of 96510 with two attachments that are linked but if you want to get a further understanding of exact L what goes into this you would be able to change to the list view um and this would give you um the option to add the transactions individually like this so you can see here that there is an asset purchase I assuming a bit of a million so this means they bought a million of this there was a the cost was 99643 and there was also two fees associated with it so you could switch between these views to get a better

understanding of exactly how this transaction um is made up of similarly to the portfolio let me know if you can't see the similar to the portfolio you could edit the transaction uh it would open the form uh you would be able to select the asset from a dropdown and then it would have the details which you could then alter in the form that would open above it and then depending on the type of asset that you picked for example if it was a treasury bill uh the transaction type and the form would change so a treasury bill would have a purchase or a sale if it was a make a principal draw a return which is when um they basically

pull money from or give money back to uh maker this would be draw a return so it would adjust based on the asset it would give you the option to add attachments and things like that too and you would also be able to in a SAR way add a transaction same form pretty much um and then this also shows the flow for adding attachments sorry add a transaction this would shows the form for adding attachments so if you needed to add an additional attachment it would open out again above the form with a user flow that people um are sort of familiar with so drag and drop or browse as well as

having a list of the attachment doents that are already stored within this uh report or workspace so um if you have bank statements they're likely to be relevant for more than one transaction so they would be stored there and you could add them individually to the transactions there'll also be a place where you can find a sort of attachment Storage Bank on the tabs and this would show the attachment as well as which transactions are associated how many attraction transactions are associated and if you clicked on these it would go back to the transaction page and filter on this transaction it would also bring your

attention to any attachments that have yet to um have a transaction assigned and basically prompt the user to click through and it would open an add attachment add a transaction with attachments already uh sort of put in there there's also other tab which basically allows for setting of global sort of variables that you could filter on so you could add here the SPV uh which you can filter on in portfolio and also here you would add service providers with uh fees um so this allows you to add a specific uh service provider fee to the transaction um and the purpose of this is for U

basically when the data is all stored with the API this will provide a a better level of analytics that are able to be performed um over the data so we can filter then on a a service provider or a fee type we can get all the foreign exchange fees we can see how much people have spending um with different combinations so that is the end of the arranger flow so once they're happy with how the report looks they've added all the transactions they have uh um they've checked that the asset amounts were correct they would then send this report completed with the attachments to the allocated Dow operator or um basically

somebody to check the report uh sort of an audit function and this shows the same view but it's now in change tracking so the change tracking is available for the ranger as well but is most relevant for the allocated Dow operator and you can see change tracking is active as this is selected here and what it basically allows user to do is to compare two versions of the same document so why would a allocated dat operator want to do this so they would take the latest version that has been submitted to them and they would then compare this against the previous version maybe one that they've already

checked and then it would bring the users attention to things that have changed so similar to if people have used vs code or maybe Microsoft Word change tracking it highlights specific areas that have adjusted uh and brings the user attention even further into what exactly has changed so here there's been two changes to two of the assets uh specifically the notional values have changed here and you would click uh one of the assets and it would give the breakdown of uh of what exactly has changed but then uh even more detailed you could then choose to open in full comparison if you had a wide

screen and this would bring your attention to exactly what has changed with the values that are changed so this is sort of the perfect feature if you're auditing or checking between two versions uh straight away you can see the size of the changes and where the changes have happened um in sort of easy formatting without spending too much time trying to F fiddle through uh the numbers then this is all good you can see the assets the change of value but why have they actually changed so to do that you would go to the transaction listing and and a similar view on the two pages you would have the same change tracking uh functionality so if we walk through an

example here you can easily quickly see there's two transactions have been added here and there's been some changes up here so the change to trans action number three is that uh the cash balance change is adjusted and there's been an additional attachment added so you would then click to open that and you would open the detailed View and immediately it was apparent uh there's been a foreign exchange fee added and the value Has Changed by 100 and there's been an attachment added so if you were a allocate a d operator you should expect to see evidence maybe provided if in the attachment uh to the new added

fee and similar to The View I showed earlier you would also be able to see in the list mode so um this even shows it slightly more clear clearly so originally there was three transactions they paid and they had one fee and now there's an additional fee that was added with an additional attachment added and the final here basically shows that this is also possible in uh in a portrait mode um but it's slightly more condensed but if you needed to access it and portrait it would be possible so that is the flow of um submitting to the uh allocated dat

operator there's a number of user stories that are um are left to complete visuals for so this is more about um suggesting Corrections um and resubmission of the of the report um as well as generating um a summary with the attachment hashes so one of the things I didn't mention that is key here is that the arranger or the one submitting the report will submit um attachments that might be sensitive or might be private but might need be needed to basically ensure correctness so the operator will be able to view these attachments but then once they're happy and they've signed off with these there will only be

an attachment hash that will be provided in the uh report that is put to um public mode and that way uh private attachments can be basically ensured that they were viewed and they were correct without being displayed uh to people that shouldn't see them um and then the final uh user stories here uh is basically the report will be submitted and uploaded to the operations dashboard or fusion and and the community or interested parties can then view this or they can use the data from the API uh to build on top of um so yes thank you T I'm I'm going to connect this to a question from Kanga

in the chat uh and question is is there a function to have a second eth address verify and the test that the action of the primary address is valid uh second eth address confirming that a bank statement is not a forgery for example and um yeah so this this is the um there's of course different levels of attestation uh and the flow that we showed has um has one type of attestation so we uh were dealing with evidence that um yeah it it might not be it might contain some private information so it cannot be uh published

directly without um it directly on the public transparency dashboard but we we still want to be able to share that evidence between uh the arranger submitting the report and uh the the operator then reviewing it and this is exactly what is happening here so every time that um an update of the report is uh submitted from the ranger to the operator the every one of those um every one of of those submissions is automatically signed and every time that the operator publishes the resulting report to the public transparency dashboard that uh that submission is uh

is signed as well with their ethereum identity and um so in this uh particular workflow uh the arranger would attach the necessary evidence with a lot of details so that the the operator can feel confident that um the reported numbers are indeed supported by the evidence and yeah the evidence should be uh good enough to um convince the operator that they are not a forgery uh this is the current version of course in the future iteration to make it more even more white watertight we can imagine um an external auditor having that role uh potentially having

access to the privileged information even within uh the financial institution itself so the the software supports this um it will be up to maker uh how far like how quickly it wants to um to yeah to implement the full uh watertight endtoend um auditing and attestation functionality but this is exactly the kind of workflows that are supported by the uh by the software and um yeah I can add a couple more comments on uh how it all works behind the scenes but uh want to give uh the opportunity to ask more questions and add

comments so if there are any questions feel free to put them in the chat and the mean time um I'll mention another thing which is I guess tying it back to the intro that I gave uh as you can see from the wireframes this is incredibly detailed and specialized uh business logic this is something that is very specific to maker and that has a lot of detail um which is important because that detail uh leads to the best practices in the organization being really captured and then when someone new joins if they use this work workflow uh they will

automatically be following those best practices because the software takes them by the handen has very specific structure that uh basically only allows them to follow the best practice that has been um defined by maker government and this is for example the critical difference between just using a strat sheeet or just using a general purpose tool that does not capture that very domain specific uh business logic and that as a result also doesn't capture the best practice as it has been discovered and as it as the organization wants to um uh to protect it and this is especially important in a decentralized

environment because you don't have the typical uh middle management command and control structure where every new employee goes through training and its only when they're following the best practices manually that you know they're they're trusted with a higher degree of autonomy um this kind of training function is part of why the software is so important because it needs to capture that best practice uh in a decentralized environment where you don't have that traditional corporate structure uh another comment I want to add is um uh the again the the fact that this is the very first business feature and

um that's why it's taking us a long time to um to finish everything up and release it uh but the way that we're building this is uh by implementing these reusable components so for example the uh ability to compare different versions of the documents side by side uh this is um this is a base functionality that will be available in the future editors that we're building um and uh so the the way that the reusable base El Els are made available uh will make it much easier for us to uh create editors like this much faster in the future so um

it's the first one that is the most difficult one uh and that takes the longest it will take a couple of iterations a couple of business features be before we have fully flashed out the reusable base infrastructure but it will take up speed and then as we keep on going um many more of these very specialized business features can be added on top at a a relatively low cost so that the organization can really go very far and defining capturing all the processes capturing all the data defining all those best practices in software so Chris is asking when it

comes to the reporting is Powerhouse monitoring the arrangers and can you explain uh how you're going to make sure that everything is in order and so it's our role to build to help the organization with the business uh process analysis which is what we've been doing which is why we've been able to come up with a very detailed piece of functionality as we've demonstrated today uh but it's um uh it's yes so we may have some role in actually running operations but generally speaking uh we are building the soft for their contributors to fulfill these operating roles so in case of the arrangers and the allocator D

operators um Powerhouse is not the arranger Powerhouse is not the operator it's the operator that will use um our software to review the reports uh submitted by the arrangers and they will publish that result to that public collaboration platform that will be uh freely uh or like that will be readily available for everyone to um uh to inspect the the published results and one of the things you'll be able to do as a a visitor of the platform is to go into the specific report going to the specific update and verify the cryptographic signatures that are

attached so that you can see that yes it was the arranger who submitted the original report and that yes it was the operator who signed off on the correctness of the result based on the evidence that was presented by the arranger and there's the Nuance there that the evidence itself might actually no longer be available because it's it's part of an NDA or something like that but the the attestation of the operator uh will be cryptographically signed and available for for inspection if uh there is ever a situation where there is a dispute or we need to go back um because the the hash of the evidence is attached anyone who can produce the

original evidence can prove that yes this was the bank statement that the operator looked at and on the basis of which they approved that report so it's completely traceable completely auditable but at the same time realistic in which uh information can be shared publicly uh we want to push that as far as possible but not be um yeah not not be too naive and assuming that everything can always be shared so we need to to cover those cases as well any other questions or comments well thank you so much for for

this it has been like very detail what you have provided during the call just to um a reminder that this is been broadcasting and so it's going to be recorded you can repeat this this goal and we're going to also provide the link for the recording since maybe it's a it's a lot of information and important information I want to uh point out about this is going to be kind of like the first call that you're going to have with the community right can we know about the next one when is going to be the specific topic and when is it going to be yeah so we're still um uh discussing internally what would be the the uh the

best topic for the next one um so we'll be able to uh to announce that soon um we'll also do it in collaboration with the with the ABCs keep that conversation going um but which one it will be exactly the next one uh when it will exactly be we still need to figure out so we will uh announce that on the Forum as soon as possible perfect I just shared in the chat uh the link of the video so you can um rewatch it I don't know if there's any a specific part of the tool that you would

really like ABCs to focus on feedback or in in general people from from make ecosystem actors if you're are very specific it could going it's going to be helpful also for us to provide you the feedback yeah so as you said it was a lot of information that was presented today so totally understand that there isn't uh a lot of specific feedback immediately um but we'll make that possible so the the the wireframe that was presented by tip uh will be able to publish that one on the Forum and then give people more time to uh review it in their own time and ask more specific questions um about the data and the flow

and everything that's related to it so we'll make that available awesome thank you so much it's been it's been a pleasure to have both of you here um we it's always you know this kind of issues at the beginning it's it's it's normal so for us is has happened a lot of time so uh we have been able to manage it pretty well and I don't know if there's any other um I don't know if there's questions or comments or if t or you wter would like to mention something before we finish the call please go

ahead yeah I want to just say thank you for having us um the uh the the presentation that we gave today will be the first one of a series so I would just uh ask everyone to keep an eye on the Forum and uh if you're interested in these uh these updates on our road map um the the different features that will be collecting feedback about and then uh yeah make sure to keep an eye on the Forum and join the next one too thanks for having us and thank you everyone for coming it has been like a lot of people wanted to know more about the update so it's it's awesome to have you all in here uh well

that will be all I don't know if T is there anything that you would like to to say before we stop the call H no that's everything thanks for having us thank you everyone [Music] bye-bye [Music] [Applause]

[Music]