-
Notifications
You must be signed in to change notification settings - Fork 58
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
Notary Application: ByteBase #169
Comments
Hi @swatchliu - thanks for submitting your application to be a Notary! The initially scored rubric can be found here: Please take a look at the notes (column I) and share any relevant additional details here in comments so we can update your score ideally within the next 2 days. Your initial unrounded score is: 2.2. |
Hi Deep, Thanks for your advice. Regarding the scoring we would like to update it as below: Individual Reputation:
Bookkeeping Plan:
That's all for our updated information. We are looking to hear from you soon. Best regards. Yours swatchliu |
Hi @dkkapur , I have some doubts about his Douyin and Wechat account, I find that his Douyin account is to publish filecoin related content starting in 2020 rather than 2018, and all articles from his wechat official account(LoT前哨站) has nothing to do with filecoin or IPFS, so I think it needs to be re-rated here. |
Hi Deep, I would like to update my bookkeeping plan No.3 with the below link. http://cloud-test.bytebase.cn/#/dashboard Honestly, this is the demo version, we will publish it on our official website once we become the notary. |
@swatchliu - I unfortunately do not have a Douyin account, but it would be great if you could share any screenshots or help clarify the claim around the account being established in 2018 as per @flyer111's comment above. Bookkeeping score increased to a 5 based on your intended plan to track applications. Your current scores for this round of elections are:
Link to rubric: However - if selected as a notary, this is contingent on your commitment score remaining at a 4 rather than dropping down to a 2. |
Hi Deep, Thanks for your great support. Please refer to the below 2 screenshots regarding the Douyin account. 1 The screenshot of Douyin for Login date and device on March 2018. You can see the last row, iPhone 6 Plus login on 20180318 2 The screenshot of Douyin for Vlog on March 2018. You can see the bullet comment was posted on 2018.3.14 3 You can also check the video of the vlog on our Douyin account via Youtu. https://youtu.be/YuK65KQf9I8 Thanks again and best regards. swatchliu |
Sorry, can you share any filecoin-related content posted with this account before April 2020? I can only see you sharing your wonderful life between 2018-2020 in this account, so I think this is your personal account before, renamed in 2020, this should not belong to the time commitment. |
1475 attenteded product launch of ByteBase, and met ByteBase's team members, who started to researched IPFS storage from 2018. As far as we know, ByteBase's platform builds a bridge between traditional companies and Filecoin network. Maybe verified data of traditional companies need an access such as ByteBase's platform to Filecoin. @dkkapur |
Hi @dkkapur , Please follow the below 2 links for the blocked vlog on Douyin which we posted in Aug. 2018 and Feb. 2019 Hi @flyer111, Thanks for your attention and ardent advice. I didn’t realize you were so focused on us. We are ByteBase. We do our hard job on the development of our platform and our programmers fix bugs to make our system run smoother and smarter. You are welcome to visit our company in Shanghai China and we’d show you what we are doing now. Could you identify yourself instead of hiding behind a new ID that signed in on June 8? We’d appreciate it if you share something useful about Filecoin ecosystem instead of commenting here. Or, you’re always free to prove yourself by putting up your own work. In addition, "flyer111" was registered on June 8 2021 which is only 17 days to now. It's too young to be an adviser in my opinion. |
In our view, any volunteer’s personal track record, especially his/her contributions to the Filecoin community, should be “inheritable’ and carried forward to the entity that he/she is associated with. We have witnessed so many folks advocating the adoption of Filecoin since years ago while their businesses were not formalized until much later. What matters are his/her proven deeds, not the form that things got done. As such, the contributions that trace back to ByteBase’s pre-incorporation stage are no less valid for all intents and purposes. It seems unconvincing to downplay or even deny a volunteer’s credits on the mere ground that his/her contributions were made in the name of an individual (as opposed to a formal business company). The foregoing principle of retroactivity ought to apply universally to everyone dedicated to the Filecoin ecosystem. We mean to deliver the clear message to the crypto-space that every person, regardless of being an individual or an entity, is welcome to be part of the Filecoin ecosystem and his/her credits would be recognized on an unbiased basis. |
@Fenbushi-Filecoin @ozhtdong thanks for sharing your opinion here as well! @swatchliu - appreciate you sharing the clips from past years. Based on the general desire to increase DataCap availability and liquidity, I think we should move forward with electing ByteBase in this election cycle. |
@swatchliu - based on this Notary election cycle's final scoring, you/your organization has qualified to be a Fil+ Notary! Per your application and the scored rubric, you will be receiving an allocation of 100 TiB. In order to confirm your participation as a Notary in the Fil+ ecosystem, please respond to the following:
|
@dkkapur Appreciate your kindness, Thanks a lot! 1.We confirm that we will focus on [Greater China Region] 2.We confirm all items below:
Confirmed.
Confirmed.
Confirmed.
Confirmed.
Confirmed.
Confirmed. 3.As mentioned before, our Miner ID is F0111007. 4.We will abide by the allocation / client due diligence plan we laid out above. 5.(Not Ready) We are preparing Ledger and we will let you know ASAP. |
@swatchliu - let me know when you receive your Ledger so we can proceed with next steps with the RKH. Thanks! |
Hi Deep, our F1 Address as below: |
Request ApprovedAddress
Datacap Allocated
|
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceadx44poyhihoomgtfoiqkrzpwuxq43i5ouhzkukfnac67wwq466y |
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
@dkkapur There was an error processing the message >bafy2bzacedf3bixnwy7ow3igh5icozkox7qfqlgqmqwvrk5cf34mupg473nmaYou can check the status of the message here: https://filfox.info/en/message/bafy2bzacedf3bixnwy7ow3igh5icozkox7qfqlgqmqwvrk5cf34mupg473nma |
This grant seems to have gone through correctly and should not be in Error status. Fixing this now! |
Notary Application
To apply as a notary, please fill out the following form.
Core Information
Please respond to the questions below in pargraph form, replacing the text saying "Please answer here". Include as much detail as you can in your answer!
Long Term Network Alignment
Time Commitment
Describe the nature and duration of your affiliation with the Filecoin project. Please include relevant Github handles, miner ids, significant projects or contributions (with links).
Stake Exposure
Please cite total token at stake (currently available, locked as collateral, vesting over time) and any substantiating evidence.
Industry Reputation
In-protocol Reputation
Please describe (in detail) your activity and tenure as a member of the Filecoin community. Please note (with links where possible) any contributions made to implementations of Filecoin, the spec, documentation, or to substantially help the Filecoin ecosystem grow.
In-protocol Security
Please describe your contributions to the security of Filecoin and the duration over which you've made contributions. Please also include any links or references who might be able to substantiate your contributions (e.g. if you've filed several bugs, please cite who you've communicated with on the Filecoin side).
External Reputation
Please describe the nature of your organization, including the country of registration, size of the organization, and time since inception.
Please share any relevant details to help substantiate information about your organization (website, named officers, links to social media profiles).
Please share any relevant external information regarding your organization (e.g. news articles, social media profiles, etc.)
Diversity and Decentralization
Use Case Diversity
(Optional) Any additional information you'd like to share about the use case(s) you plan to support?
Allocation Plan
Concreteness of Allocation Plan
Allocation Strategy
How do you plan on allocating the DataCap requested above? Please describe your allocation strategy with as much specificity as you can.
Are there any internal processes you plan on impelementing regarding the target, amount, or rate at which you'll allocate DataCap?
How do you plan on securing the DataCap to ensure your organization (and its delegated members) are the ones allocating the DataCap?
Client Due Diligence
How will you vet your Client to ensure they are spending that DataCap responsibly?
What questions will you ask to ensure the Client can properly handle the DataCap you intend to allocate to them?
What processes will you employ to confirm that a Client is not improperly over-allocating DataCap to a single entity?
Bookkeeping Plan
Do you plan on keeping records of your allocation decisions? If so, with what level of specificity do you intend to respond to any audit requests?
Do you plan on conduct your allocation decisions in public (e.g. Github repo), private (e.g. over email, Telegram, etc), or both?
Track Record
Past allocation
Have you previously received DataCap to allocate before? If so, please link to any previous applications.
Cumulatively, how much DataCap have you previously successfully allocated?
Have there been (or are there still) any disputes raised against you from your previous DataCap allocations?
The text was updated successfully, but these errors were encountered: