Post #31811

27242b556317d204596bb20c828b2ed7c843d7fa6bd601e88b0688f001b442da
e7946ddb04f6aeaa661903e0afa14d9691c4e073c875d316cd32ae15520ef63b
e2c61429397da55a5ee7749088023feb12e0e8e261dfeba32ee7c0794f9a12f8
Signature verified

The signature from the blockchain entry has been verified against an identity on this server.

{"entry_date":1613465672,"post_data":{"edit_count":2,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"19cb11e8f5734926aa8453fc2ca01bfca4ff40956dde8b6bc5610363d4c576a921e3e8200f4c015652f97435d805fd968f515aeef5e8e5230d56572984611242","node_id":115,"post_date":1613465609,"thread_id":5666,"user_id":35},"post_link":"https:\/\/forum.factomprotocol.org\/threads\/sphereon-bv-niels-klomp.5666\/post-31811"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
[Sphereon BV] Niels Klomp
I had convos with some developers in community, we discussed the idea of moving tokens on the protocol level (L1).

L2 solutions is not really popular (even L2 of popular L1’s like Ethereum), and in our case Factom is not popular as L1 itself, so FAT as L2 is not popular at all.

In my opinion tokens balances and transactions should be operated on L1, like in Ethereum. Ethereum has tokens on L1 and it’s pretty straightforward for anyone to create own tokens, which leads new developers into Eth (not only this of course, but it's also important).

I think it’s not too late for Factom to do it. We can use some existing FAT standards and algorithms and implement them on L1, expand Factom libs and factomd APIs.

What do you think about this direction of development for Factom?
This is the raw content, without BBCode parsing.
Top