Replies: 6 comments 6 replies
-
I like the idea of a partnership here, and think that BlockRank is an interesting example of some functionality we could potentially use as a proof-of-concept for API widget.
Not so sure we need their automated airdrop functionality vs. our own, but would be interested to hear technical POV about pros/cons vs. what we use today.
Also interesting...but maybe as a service thought API vs. for our own airdrops, as I am not sure that gaming our rewards is an acute concern based on weekly payout remaining very consistent.
Summary: if the 6000k USD of ASASTATS is primarily meant for 2/3/4 - probably not worth it. If it is meant to secure API licensing/integrations...could be worth it, but I think we'd need to understand the use case/s where this widget is then considered valuable to our end users. I think the most ideal partnership we are looking for is one where ASASTATS and BlockRank provide equal value to each other - I think the proposals above are all primarily ones where BlockRank is purely selling us a service. |
Beta Was this translation helpful? Give feedback.
-
We've invested in our own solution and for abandoning it we should have plenty of good reasons, like a pretty solid assurance for enough exposure of that joint promotion. |
Beta Was this translation helpful? Give feedback.
-
Afaic this one is a major obstacle for partnership based on the proposed points. The approach from the very start in ASA Stats has been very simple: if you are qualified for rewards and airdrops then your obligations ends at the moment you receive ASASTATS. The matter of fact is that we simply don't have an institute to prevent sending rewards and airdrops to anybody, no matter if they for certain are those airdrop farmers. Our only condition has been - and will remain in the pre-DAO phase - that they are qualified for a reward/airdrop. |
Beta Was this translation helpful? Give feedback.
-
|
A fair partnership offer here is asastats.com introduces a widget for their service (so users interested in the service can pay for it) and they provide us with their API. Anyway I see no reason for using their API currently. I think it's too early for the partnership and I suggest getting back to this when widgets API is available. Their partnership offer, i.e "Joint promotion of one another's projects is a given as well!" sounds interesting. Do we know how much traffic can they provide? |
Beta Was this translation helpful? Give feedback.
-
After Davis introduced us to their project, this is exactly what we proposed and pointed out during the meeting as our primary interest for partnership. |
Beta Was this translation helpful? Give feedback.
-
They don't offer their services yet, so I guess they and we can only speculate about that. |
Beta Was this translation helpful? Give feedback.
-
|
I agree with the others points of: does the team need the 4 services? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that's basically that. We are interested in that first point, but as DragMZ pointed out that won't take place until our user widgets are available. |
Beta Was this translation helpful? Give feedback.
-
|
I think a partnership would be amazing..... Even though I I'm not sure how the airdrop automation would benefit ASA Stats (I don't think there is an airdrop or plan to be one) so I would suggest a draft be made and see how this partnership benefits us at ASA Stats before we can make a considerable decision regarding this |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for editing your comment, but we may use whichever name comes to our mind (of course we prefer ASA Stats, but every other example is fine like ASAstats, asastats, asa stats, ASAstats.com, asastats.com, www.asastats.com, ...) for the project except for ASASTATS as we are everything but a token project. |
Beta Was this translation helpful? Give feedback.
-
|
A follow-up from Davis:
I'm going to reply in the next two days with the excerpts from this discussion. Any thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Davis! We had conducted a discussion about your proposal (#11) and its main points are that we can have use of your future API and that, unfortunately, your proposal isn't acceptable for us. The first aspect of your proposal is the allocation of tokens, but we have invested in developing an in-house solution for the purpose and we are more than satisfied with it. The other aspect is checking and surveillance of airdrop farmers, but the matter of fact is that we even don't have any institute and mechanism for punishment in ASA Stats! Our tokens are allocated based on very strict conditions (being qualified for airdrops, rewards for contributing to the project, ...) and once they leave our pools the receivers can do whatever they want with them. Nevertheless, we are indeed interested in your project, but completely from our users' perspective, and not directly from ASA Stats'. Once your API is published we'll be sponsoring the development of ASA Stats User Widgets (point 16. in our roadmap https://github.com/asastats/docs/blob/main/roadmap.md) which uses your API for delivering your content to our users' pages. Once your API is developed we'll have a discussion should we purchase your API by ourselves or we'll leave that part to the actual third-party developers of BlockRank-based ASA Stats User Widgets. Sincerely, Ivica |
Beta Was this translation helpful? Give feedback.
-
@AlgoRhythMatic and I had got a meeting with BlockRank a few weeks ago, got familiarized with their service, here's AlgoRhythMatic's report from that meeting:
Summary: a nice productive meet-and-greet! ASA Stats has made an informal connection with Davis from BlockRank, and had the opportunity to communicate what we are looking for in terms of a future API integration for a widget down the road.
And this is my very recent email communication with Davis:
Hi Ipaleka,
I wanted to reach out to you with a proposal for a strategic partnership between ASAstats and BlockRank. We would love to partner with you all to help with your token distributions (i.e. airdrops) and collaborate on potential API endpoints you may be interested in. I've included a potential partnership proposal below.
BlockRank provides:
One year service of the following:
We are only forming between 5-10 strategic partners. We are in a product development cycle and really want input from folks we trust to help us add features that people will find useful. The benefit for you is - if you have something you need from an analytics standpoint, we'll add it to our backlog and likely build it for you!
ASAstats provides:
6000 USD equivalents of the ASAstats token (1-year vesting schedule) at the current ASAstats market price.
Joint promotion of one another's projects is a given as well!
Looking forward to hearing your thoughts.
Davis
Hi Davis!
Thank you for your email and consideration. Based on the ASA Stats' base principle, we have to discuss every discussion with the community.
Is there some information from this proposal that you don't want to be publicly exposed?
Sincerely,
Ivica
Not at all! Please share with your community.
I will, thank you!
So I'm opening a discussion about their proposal.
Beta Was this translation helpful? Give feedback.
All reactions