Pages:
Author

Topic: [ANN] FACTOM - Introducing Honesty to Record-Keeping - page 470. (Read 2115876 times)

full member
Activity: 183
Merit: 100
So FACTOM servers aggregate the hashes from all of their clients into one megahash and commit it to the blockchain every 10 mins while giving cryptographic proof to each client that their hash was indeed included into the megahash?
This is a nice way to cut costs for your clients, albeit your solution has a single point of failure - FACTOM servers. Still some gov and corporate entities may be interested in using your service.

What I did not immediately understand after looking at the paper is why you need your own coin and your own chain?
Can't FACTOM be a subscription-based service where you hand out API keys to your clients to push the hashes to your servers?

Decentralized autonomous applications for the most part require their own token, if the actions of one party in the application obligate the protocol to provide services.

So let's use Factom as an example.  At first, it would seem that anyone placing an entry into Factom could use Bitcoin to pay for that entry.  But that means there would be a Bitcoin transaction for every transaction in Factom.... That would bloat the Bitcoin blockchain just as much as putting hashes directly into the Bitcoin blockchain, and it would require a Bitcoin transaction fee for every entry PLUS the Factom fee, so that fails as a solution.

But what if you use Bitcoin to purchase a bunch of entries.  That would solve the bloat problem and the cost problem.  A user could buy say 100 or 1000 entries in Factom, then use them up within Factom, then buy some more, then use them, and so forth.  But now we have to figure out who the user buys those entries from.   Is there a special owner of Factom?  Or could just anyone sell these entries?  And if just anyone can sell these entries, then why buy them from someone else?  Why not just buy them from yourself?

So the way that Factom allows the selling of those entry rights is to issue and support our own token, the Factoid.  Servers and auditors that keep the system running are rewarded Factoids for maintaining the system.  Those Factoids can be converted into Entry Credits, so anyone holding Factoids can in fact provide a "Store Front" service for Factom users.  The "Store Front" can accept Bitcoin, convert Factoids into Entry Credits, which get assigned to the public key of the Factom user buying those credits.

The User never has to see a Factoid.  The User can pay Bitcoin (or even dollars) to a Store Front that in turn provides the User Entry Credits that can be used to put entries into Factom.

In other words, these Factoids represent an potential obligation of the Protocol to provide a limited amount of processing (i.e. adding entries into Factom).  Factoids can be freely traded.  Anyone with Factoids can use Factom, but more importantly, anyone with Factoids can allow someone else to use Factom.

An application coin simply represents a limited obligation of a Protocol, rewarded to someone for providing support for the protocol.  Distributed applications will almost always require a token if the application requires something more complex than a simple fee for service to drive the application.
legendary
Activity: 1722
Merit: 1000
Glad to see the Factom Project progress! Also nice to see collaboration with other personalities in the space to advise on a well written whitepaper!
full member
Activity: 152
Merit: 100
So FACTOM servers aggregate the hashes from all of their clients into one megahash and commit it to the blockchain every 10 mins while giving cryptographic proof to each client that their hash was indeed included into the megahash?


also, Factom Blocktimes are not restricted by 10 minutes

"Factom Blocks – where the Merkle roots from Entry Blocks are entered to form another Merkle tree with a final Merkle root, which is computed every one minute and inserted into the next Bitcoin block roughly ten at a time"

http://cryptobizmagazine.com/the-facts-on-factom/
full member
Activity: 152
Merit: 100
So FACTOM servers aggregate the hashes from all of their clients into one megahash and commit it to the blockchain every 10 mins while giving cryptographic proof to each client that their hash was indeed included into the megahash?
This is a nice way to cut costs for your clients, albeit your solution has a single point of failure - FACTOM servers. Still some gov and corporate entities may be interested in using your service.

What I did not immediately understand after looking at the paper is why you need your own coin and your own chain?
Can't FACTOM be a subscription-based service where you hand out API keys to your clients to push the hashes to your servers?

Great points - Factom network has its own access token to prevent spam (just like Ether to Ethereum). The Factom servers will be a distributed model designed to only process Factom transactions. The purpose of Factom is to provide DApps/Dacs/DAOs/Data processing companies or even Transaction processing systems like back-end exchange platforms, with the benefits of using the Blockchain technology, but without the time and data constraints of the Bitcoin Blockchain.

Factom can support a subscription service where people can use an API to send their data, that is certainly part of the vision - the hashing of the data itself can be done client-side and would then be rehashed by Factom to compile into a Factom block.
 
Thanks for reading the whitepaper
full member
Activity: 202
Merit: 100
So FACTOM servers aggregate the hashes from all of their clients into one megahash and commit it to the blockchain every 10 mins while giving cryptographic proof to each client that their hash was indeed included into the megahash?
This is a nice way to cut costs for your clients, albeit your solution has a single point of failure - FACTOM servers. Still some gov and corporate entities may be interested in using your service.

What I did not immediately understand after looking at the paper is why you need your own coin and your own chain?
Can't FACTOM be a subscription-based service where you hand out API keys to your clients to push the hashes to your servers?
full member
Activity: 152
Merit: 100
legendary
Activity: 1630
Merit: 1000
Cool project, I may be getting involved in the crowdsale
legendary
Activity: 1268
Merit: 1006
We're talking about Blockchain bloat and beaming Peter Kirby (President of Factom) to our Meet Up at Decentral.Vancouver on Thursday: http://www.meetup.com/decentral-bangtown/events/218623952/
donator
Activity: 2352
Merit: 1060
between a rock and a block!
Glad to see you've released your whitepaper... Hopefully you are getting good feedback from reviews.
sr. member
Activity: 251
Merit: 250
This post and much of the thread's content is out of date. Please refer to this new thread for up-to-date information on the Factom protocol.


INTRODUCING HONESTY TO RECORD KEEPING

Factom is a system for securing millions of realtime records in the blockchain with a single hash.
This gives you the tools to build applications with all of the security of the blockchain without the speed, cost, or size limitations.
Our goal is to involve the Bitcoin and Crypto community to engage with us, look at our work, and collaborate with developers across the industry
and beyond.

Factom is a next generation platform for creating enterprise tools and applications using Blockchain technology.
Factom allows you to build applications on top of the Bitcoin blockchain. Factom uses a simple API that lets you build projects that were not possible  
before while still harnessing the trust and security of the Blockchain.

Factom is a solution to:

  • Blockchain bloat
  • Off chain transactions
  • Use cases and project ideas for hashing data into the blockchain

In a nutshell, what is Factom?
Factom is a system to record entries in a way that makes the list unique (everyone gets the same copy) and allows anyone to add to the list, but does
not allow anyone to change entries once they are in the list.

As a designer of business applications, why should I consider using Factom?
Factom is a method of creating an immutable audit trail. It is also a mechanism to communicate changes in a system. If your application needs a
central server to coordinate processes, you might be able to eliminate the central server in favor of using Factom.

Does Factom use a cryptocurrency?
Yes. You can use Factoids (the Factom currency) to purchase Entry Credits with a simple transaction. The protocol does the conversion, so you
effectively purchase the Entry Credits from the protocol. You assign those Entry Credits to a public key.

Who controls Factom?
Factom is a distributed, decentralized protocol running on top of Bitcoin. That means nobody controls it, but that it is software that people all over
the world run to make the protocol work.

Factom.org is releasing and maintaining the software. But the software is open source, and anyone is free to use it for any purpose.

With Factom is really possible to build safer and more secure record keeping on a truly global scale.
There are three types of proof that allow Factom to do that:

  • Proof of Existence: a document existed in this form at a certain time.
  • Proof of Process: a document existed and is linked to this new updated document.
  • Proof of Audit: an updated document can be verified to have changed according to a set of rules.

Docs & Demos


Partners & Collaborations

Pages:
Jump to:
© 2020, Bitcointalksearch.org