-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driver & Network Selection - new mechanism #3023
Driver & Network Selection - new mechanism #3023
Comments
@grisha87 @shadeofblue @nieznanysprawiciel - above ticket is a conclusion of our Friday discussion regarding default network/driver selection on Allocation creation. Please verify it that looks OK from your perspective (SDK - JS + Python) |
Blocked till feedback is gathered. |
To the AC I would add that the pre-release containing the fix should successfully pass the tests on https://github.com/golemfactory/golem-js/actions/workflows/release.yml How to run it:
Success criteria
|
Suggestion:
|
re: example D -> my expectation would be for yagna to give me the "recommended" platform that will satisfy the requirement that I have given in my request -> so, in other words, my interpretation of the request is: give me the "default" of those platforms that support the or, in yet another set of words, give me the default mainnet platform... such as it implemented, it will prevent forwards-compatibility of allowing the SDK to select the default mainnet platform... e.g. if we wanted to switch from |
uh, it would be good to conduct also tests with other requestor products as JS SDK is very far from the only consumer here ;p |
Added pull request |
back to development on request of @nieznanysprawiciel - 1MD |
RC 14 has those changes |
Context:
Currently configuration of payment platform (driver + network + token) is done by application. It has some benefits, however also introduces important problems:
Consequently, we want to change our approach and get rid off precise specification of payment platform on allocation creation (flow between SDK → API → Yagna requestor).
Solution:
Payment Platform:
Payment Platform consists of 3 values: driver, network, token
We want:
erc20
(underneath new payment driver will be hidden - Rename erc20next to erc20 #3019)holesky
fortglm
andpolygon
forglm
erc20
or/andholesky
it should returntglm
. For values oferc20
or/andpolygon
it should returnglm
Allocation Creation
SDK will create allocation in following fashion:
Example A: default driver, netwrok and token:
Request:
Alternative Request:
Response:
Example B: default driver on polygon
Result:
Example C: full platform specified
Request (backward compatible):
Alternative Request:
Result
Example D: default driver and network for glm token:
Result:
Acceptance Criteria:
Additional Information:
The text was updated successfully, but these errors were encountered: