Search results

  1. PaulSnow

    Amendment Doc 107 - Factom Grant Process

    Great work David. Of course, I continue to not like closing discussion threads until the whole process is complete, but I'll not bother beating that dead horse here. Otherwise, a couple small comments, but really, great job.
  2. PaulSnow

    Grant Update [Factom, Inc.]-014 Anchor Master

    We are currently anchoring into Ethereum. We have a post on the topic in prep.
  3. PaulSnow

    Grant Update [Factom, Inc.]-013 Oracle Master

    Description Exchange rates for FCT to Entry Credits are important in order to maintain a target price for entry credits of 1/10 of a cent. As determined by the Standing Parties and the Authority Set, the Oracle Master will record into Factom relevant market information to establish the trading...
  4. PaulSnow

    Grant Update [Factom, Inc.]-014 Anchor Master

    Description The Anchor Master is in charge of ensuring anchors are written in a timely way to the Bitcoin and Ethereum blockchains. This grant covers the cost of developing and maintaining anchoring code, deploying and maintaining the anchoring code on to servers, and monitoring the software...
  5. PaulSnow

    Media Pack Update for Newly elected ANOs

    Sorry for the slow reply. I'll try and get this done.
  6. PaulSnow

    Guide Pay: June 2019

    I like the current amount, think the guides have done an amazing job, and I'd like to support them in any way I can.
  7. PaulSnow

    Factom Inc and Communication

    I started to write a long response, but in reality (while I might quibble on a point or two) most of what you are suggesting is good, and we should take action on those suggestions. I might also suggest that the community take up so many of these opportunities and run with them as well. For...
  8. PaulSnow

    Factom Inc and Communication

    I think we can get so busy working on code and working to address concerns that we don't respond quickly to these kinds of food suggestions. I agree that our public communication has been too sparce on AMAs, chats and such. And I believe the token value is critical to our ecosystem. I'll...
  9. PaulSnow

    Approved Grant [DBGrow-004] FAT Development 3

    I am looking forward to contributing where I can to the development of the FAT protocol on Factom. It is one of my dreams.
  10. PaulSnow

    Approved Grant [Factomize-004] Core Development

    Who has done fantastic work. And the one thing this ecosystem needs is developers like @Who . (Why do I keep thinking there must be a baseball team in this discussion?)
  11. PaulSnow

    Withdrawn Proposal [BEDROCK-DEFACTO-002] Factom Identity FIP and Open API Integration

    Even if you withdraw this grant, please let us keep the communication going about Factom based Digital Identity with your team.
  12. PaulSnow

    Approved Grant [TFA-002] FAT-Integration in TFA-Explorer

    FAT integration is likely very huge. I'm not sure if there is anything out there that might compare to what we can do with FAT and an Explorer with FAT support. I looked at Etherscan, and it does a bit for looking at ERC20 tokens, but it isn't as intuitive as it could be.
  13. PaulSnow

    Approved Grant [TFA-001] FAT Firmware Upgrade for Ledger Nano X/S

    I think this grant is pretty exciting!
  14. PaulSnow

    Approved Grant [BIF-Factomatic-003] Verifiable Credentials FIP

    Identity and tokenization isn't by any means settled. Look at the specs and try and find how identities are issued and keys are rotated. Or with tokenization, how tokens and securities are issued, documented, managed. The world remains pretty fresh. Working together we can make a mark, but...
  15. PaulSnow

    Approved Grant [Factom, Inc.]-015 Protocol Development

    We would like Parchment to be a fast follow, so in the June time frame.
  16. PaulSnow

    Approved Grant [BIF-007] Identity, DID and signing FIPs

    Please remember nearly all of our Identity work has been done in public, with the community, and not only for our projects, but in support of other grants. We don't want to change that, but continue it. I think it would be wonderful to be working more closely with you. Like Sam pointed out...
  17. PaulSnow

    Withdrawn Proposal [SPHEREON-006] Core Development Coordinator

    BTW, I am not opposed to documenting what we are working on to do the refactoring, and when we get to the point of deciding to make protocol changes as part of refactoring, a FIP would be appropriate. We have been discussing the current work in our monthly reports, and will do so through these...
  18. PaulSnow

    Withdrawn Proposal [SPHEREON-006] Core Development Coordinator

    The only push back I have in the list is that improvements are not changes to the protocol, and are not high level enough to rise to the need of a FIP. Again, I point to BIPs and point out that over the 8 years BIPs have been proposed, only 322 have made the list. The process looks like this...
  19. PaulSnow

    Approved Grant [Factom, Inc.]-015 Protocol Development

    From Github and the CLA.txt one can see all of these developers. In addition we have Steven who I just noticed has not added his name yet, nor has Clay, or a few others. Carl is not a developer, but provides project management and support. Paul Snow Factom...