You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to upload data: http://localhost:8000/contract/dataUpload/
{
"estimate":true,
"description":"ds",
"link":"http://link.com",
"no_restrictions":false,
"open_to_general_research_and_clinical_care":false,
"open_to_HMB_research":false,
"open_to_population_and_ancestry_research":true,
"open_to_disease_specific":false
}
Token e5cb20b3acaa59631d25f80b4197f24464998bbe
But i get the error:
UploadDataPrimaryCategory '0x2a4b4f04cc558cf3afc7114331dfe91cac5a1ae2979c668fbcb8253843924220675eec0870caf389f69e20c5c101225bf1dfa0e48a534e3f062db3520c7eb1a1' - '0x2a4b4f04cc558cf3afc7114331dfe91cac5a1ae2979c668fbcb8253843924220675eec0870caf389f69e20c5c101225bf1dfa0e48a534e3f062db3520c7eb1a1' is not a valid ETH address
I believe that the error can be fixed by updating the eth address of the provider to a correct eth address.
This cannot be done because the following two methods don't work:
Creating a user while specifying an Ethereum address
Update user info at `[http://localhost:{{port}}/user/authenticated/update/
The text was updated successfully, but these errors were encountered:
to create the user i used the code in the example:
{
"last_name":"piccini",
"email":"[email protected]",
"password":"password123",
"create_wallet":true,
"user_type":0
}
which generates a new address.
Reading the error it appears that this eth account is not valid, so i was trying to change it.
I was trying to upload data:
http://localhost:8000/contract/dataUpload/
{
"estimate":true,
"description":"ds",
"link":"http://link.com",
"no_restrictions":false,
"open_to_general_research_and_clinical_care":false,
"open_to_HMB_research":false,
"open_to_population_and_ancestry_research":true,
"open_to_disease_specific":false
}
Token e5cb20b3acaa59631d25f80b4197f24464998bbe
But i get the error:
UploadDataPrimaryCategory '0x2a4b4f04cc558cf3afc7114331dfe91cac5a1ae2979c668fbcb8253843924220675eec0870caf389f69e20c5c101225bf1dfa0e48a534e3f062db3520c7eb1a1' - '0x2a4b4f04cc558cf3afc7114331dfe91cac5a1ae2979c668fbcb8253843924220675eec0870caf389f69e20c5c101225bf1dfa0e48a534e3f062db3520c7eb1a1' is not a valid ETH address
I believe that the error can be fixed by updating the eth address of the provider to a correct eth address.
This cannot be done because the following two methods don't work:
The text was updated successfully, but these errors were encountered: