Open kozayupapa opened 1 year ago
opsci wtf-cache: https://github.com/opscientia/wtf-cache/tree/main
I cloud run cache-updater locally and succeed to get data from contract through JsonRPC gnosis, mumbai.
(base) wtf-cache % ANKR_MUMBAI_ENDPOINT=https://rpc.ankr.com/polygon_mumbai ANKR_GNOSIS_ENDPOINT=https://rpc.ankr.com/gnosis node src/cache-updater/cache-updater.js
Using production database
env: https://rpc.ankr.com/gnosis
cache-updater pid: 64706
and then start server
(base) wtf-cache % node src/cache-server.js
Using production database
cache-server pid: 60517
Server running in http://127.0.0.1:3001
getAllUserAddresses: Entered
getAllUserAddresses: Retrieved addresses from database. Returning.
then we can get data from contract and cache to sqlite
(base) database % curl "http://localhost:3001/api/getHolo?address=0x27b1c26c1bf6f8bee59327691b8af8d9d0953d35"
{"gnosis":{"name":"Sina Iman","bio":"Engineering @ DeSci Labs 👋😎","orcid":"","google":"","github":"","twitter":"","discord":""}}%
Greetings I am an engineer participating in an online hackathon called HackFS 2023 at ETH GLobal.
I learned about the opensci project as an introduction to an advanced case study of collecting data in filecoin. We are looking for something to contribute to OpenData, distributed science at the HackFS event.
The idea is to create a generic mechanism to store reviews from scientists on already collected data on a distributed file system and make it available from any smart contract.
We are referring to the following code as a mechanism to prove that you are a scientist.
https://github.com/opscientia/verse
May we connect to the following smart contract in this hackathon and use the data of the scientists already gathered in the demo?
https://opsci.gitbook.io/interacting-with-the-wtf-protocol/reference/api-reference
Also, please let us know if there is a good way to add our Identity data to the contract for testing.
and also ask to support-filecoin channel on Discord.
Hi filecoin team. I learned about opsci's efforts by reading the advanced case study on filecoin. (https://fil.org/blog/case-study-opsci-how-an-open-science-commons-project-built-on-web3-infrastructure-empowers-community- discovery/)
We are thinking about what we can contribute to distributed science with this hackathon.
We refer to the following code as a mechanism to prove that you are a scientist. https://github.com/opscientia/verse
Some individual scientist proof data already exists in SmartContract, such as gnosis.
We would like to discuss whether we can use this data in our demo, and if you know someone from OpenSci, could you introduce us?
I got a Twitter response from OpSci mainter. To summarize what I've heard, I've heard a lot of things.
A. changed to new app uses particle network to create a wallet for a user and verify a scientist's web accounts using a simple smart contract registry. B. it is ok to use the old one for PoC
===
Candidates for how to proceed
== I think I prefer to proceed with 2. I think it is better to proceed with 3 if we can get information directly via TwitterDM that will eliminate the negative of 3, and with 2 if we can't.
I'm trying to use local PC lotus node. I tested DL data which CID is on following site. https://datasets.filecoin.io/google-open-images?page=16 I installed lotus with brew to my macbook. original data download instructions of above site says lotus client helper retrieve XXX but it cause following error
No help topic for 'helper'
if I cut helper option, it cause another error.
lotus client retrieve --miner f096540 bafykbzacedojx7clth6jn6bvx6i2cpfnhvioonnodtukjolv3y6paplokynxc @/data/maris/google_full/open-images-dataset-train3/farm5.staticflickr.com/9.zip
ERROR: could not get API info for FullNode: repo directory does not exist. Make sure your configuration is correct
Shoud I use another way to install lotus?
I agree with going with candidate 3 however you seem more knowledgeable in this so I suggest we follow your decision.
Priority: High
Priority: Medium
Priority: Medium
Priority: Low
Priority: Low
Priority: Low
Priority: Low
Priority: Low