Episode 281: Devconnect 2025 With Devansh Mehta  [[3. Resources/Readwise/Full Document Contents/Articles/Episode 281 Devconnect 2025 With Devansh Mehta|Full Document Contents]] ## Document Notes ## Highlights - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 14, 2026 at 11:24 PM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 12:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 1:25 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 2:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 3:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 4:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 5:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 6:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 7:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 8:24 AM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 12:03 PM - have to answer the question that how do we actually sustain this for the long haul. So that's basically my work which is looking at these different open-source repos figuring out where the funding is coming from and I can divide that into two parts. One is where the money is coming from and the second after the money comes how do we divide it between these different open-source repos. So I call that the credit assignment problem. who deserves how much and the funding loop problem. How do we actually get the funding to assign according to the credit which is ([View Highlight](https://read.readwise.io/read/01khfhhnxey9r08m1znxz2y6ry)) - Tags: 👻 ai highlighted - it can be different for different projects. One project uses a dependency a lot another uses it in a marginal way. So the second step is giving a value to that dependency graph so that it's weighted and then the third step is finally putting money into one public key and it gets sent across the entire graph base based on the weights and edges. So that's the larger framework that we should be operating in for connecting cost and revenue centers. And then the thorny question which I'm happy to get to next is how do you actually ([View Highlight](https://read.readwise.io/read/01khfhhp0jfdy819detyenqxm5)) - Tags: 👻 ai highlighted - and remove that bias for the sustainability of projects in the long run? So basically I think of funding mechanisms as like a Netflix algorithm. A Netflix algorithm shows you what movie to see. So funding mechanisms show you how much money a particular project should get. And honestly the alternative to this which a lot of open source repos do today is the RFP process. And I've actually dug a bit deeply into the open-source funding outside of web 3 as well. And it basically operates through a request for proposals where in good ([View Highlight](https://read.readwise.io/read/01khfhhp868byjps5y619aqfx4)) - Tags: 👻 ai highlighted