1) With the blockchain being live, can smart contracts be

created and deployed on the LGCY Network? Or the network doesn't yet have that functionality?

I think @Jomikel can answer that it pretty great detail!

Wow.... Sorry... Each LRC20 token is a Smart Contract. So yes, in theory we can deploy smart contract. But currently there is an issue with deploying

Good question. We need to measure not directly in complexity. But in runtime execution. A smart contract can do stuff and trigger another contract which is doing stuff and so on. No Problem. But there are some limitation. For example: Its not possible to query some offchain data directly or to generate random number. And if the execution tooks too long (because of the complexity of the contract/code) then a timeout occurs and the tx fails. Did you have some "specific" in mind. Maybe i can answer better if i know what exactly is the question. Complexity is a very generic term

Ah okay! I see! Well, the second part in my two part question was 2) With the ability to start and finish transactions, as well as the ability to create smart contracts, everything seems good to go. That being the case, what is the current set back for the projects that would like to launch if everything is good to go and the chain is live. But you have expressed excellently one of the current setbacks that is stopping progress forward. The deployment errors and the time out issue (presumably everything needs to be streamlined to avoid the time out) This technical insight is incredible and is something that I know the community really wants more clarification on. These types of explanations and answers, give more context to the phrase "soon" Soon meaning, there are still some things to work through. So this is awesome. Secondly, if I had to ask specifically: What type of errors are you referring to when you say that if you deploy, you get some strange errors. Like things just flat out not working? Or the error messages are not consistent with what is being shown? Things only functioning half way? Could you go into a bit more detail?

Haha please take your time! I appreciate you!

Not sure how i should describe that all. I try to start with my special power: Tech stuff. That timeout "issue" at calling Smart Contract functions is not directly an issue with the Blockchain. More a mechanic to prevent the Blockchain against contract executions wich are runs in a endless loop or really long tasks. In the worst case sich contract executions can halt the whole blockchain if the chain waits for execution end. To control the timeout there is a chain parameter (#10) which can be changed with a governance proposal. Current value is 50ms. And yes, if this happens then the contract developer is in the need to fix the contract to more performance. Because of the error for which we cant deploy contracts: Better to ask Justin with this topic..... I can tell you that the error message says something like: "request entity too large" Because the other projects like Lazy Monster Space Club which are waiting for "something": I would love to build my very first Legacy dApp (Just a demo app) but i cant. Im on the same position: Need to wait for the team to fix at least 3 issues: 1. Auto-Logout at the Chrome extension. Sounds strange, but a dapp needs to be connected with the extension. But after the uncontrolled wallet logout of the extension the dapp is not able to communicate with the Bockchain which results in a non working app until the extension is unlocked again. 2. The Chrome extension communicates with the backend nodes only via HTTP (not HTTPs). So if the dapp is hosted on webserver with HTTPs then we will got only errors because "cross security communiction". That means a dapp needs to be hosted on HTTP only to "work". 3. The Chrome extension has trouble to communicate with the "fullnode" which is configured in the chrome extension. (Gateway timeout). Its not an issue with the Blockchain or that fullnode but with the Network infrastructure. (I guess its a problem with revers proxies) Unluckily we can't setup other fullnodes to use.

Wen fixed @WesWadejr, I wanna see Jo's fluffy unicorn dApp.

lol no. No graphics 😛

soon

I knew it.

I will still call it the fluffy unicorn dApp.

https://unicorns.legacy.chainmasters.ninja/

Jo, thank you so much for shedding some light on these issues. People tend to forget that blockchain and web3 is still relatively new, and there are many hurdles to overcome. So to Overgeneralize the word "soon" to mean that nothing is happening, when in actuality: the actual explanation of what is going on in the background will just go over most people's heads (myself included) isn't right. So it's great to see some of this stuff cleared up. And now at the very least, if people are asking what the hold up is, we have a small frame of reference into what the answer is. This was incredibly helpful and I truly appreciate your time and effort into writing all this

At first: Many thanks. I try to do my best to "Providing Clarity". Hopefully the other Chainmasters will do the same "soon"... ^^

Lmao that was great. And OOOOHHH chainmaster! I get it now! Lol that also went over my head

Issue 1 is (i guess) self-made by the LGCY devs. The chrome extension is a fork of "TronLink" (Number one wallet for the Tron Blockchain). TronLink dont have that auto-logout issue. To fix that should be not a big deal. (imoh). On the other side i need to say that i never takes a look at the sources of TronLink. Maybe the code is something like a big bag of spaghetti code 🤷‍♂️ Issue 2 is not directly an issue. More a security feature of the browser. The browser dont accept sending HTTPs requests from websites which are hosted at HTTP. Thats normal. But unfortunatley the configured Node in the chrome extension is a blank IP. (No HTTPs with IPs, only with domains). That can be fixed in 5 minutes. But it needs a new version of the Chrome extension :( (Just as a side note: On TronLink we can manually add/remove cusom nodes, but that feature is not available in the LGCY chrome extension) issue 3: It's hard to estimate because I have no insight into the Foundation's infrastructure. Im using myself a typical infrastructure with some reverse proxies. If i doing something wrong in the config in one of them then i have exact the same issue at my infrastructure. But my infrastructure is (i guess) a lot smaller than that from the foundation. And im hosting and configuring all my stuff for myself. If i right remember the Foundation is using some infrastructure providers like cloudflare. I guess its much more complicated to handle such a big network.

Haha spaghetti code. Do you know if Tronlink is open-source? So with #2 when you say a new version, you don't mean start from scratch do you? I know new versions of things happen all the time 1.19.1 1.19.2 1.19.3 Stuff like that. And for #3 ah I see, that's an extremely fair point. No way of getting a read on that

Yes, TronLink is open source. #2 Hell no. I just meant that the LGCY devs are in need to make an update of the extension and publish it on the chrome webstore. Something like version 1.0.3 Its not possible to hot fix it.