Quote from: Mandelliant on August 18, 2017, 01:47:43 AM

Quote from: mig6r on August 17, 2017, 06:34:20 PM

Quote from: mig6r on August 17, 2017, 05:27:57 AM

Quote from: mig6r on August 15, 2017, 06:50:41 AM

Ok, but you would always be dependent on updates by the Ethereum community, right? I was also wondering how all those VR projects plan to efficiently run on the blockchain as that is insanely memory intense. But so far I didn't get an answer.

So is the memory intensity a problem or not? I always think about that when I hear VR on the blockchain. VR is slightly more intense than transactions -.-

Why does nobody bother to answer my question? Cheesy

Isn't it a valid one? I mean, I think that block size limits could severely limit the capabilities and functionalities of such a platform. Or what am I missing?

At present the transaction volume is not a limiting issue for BitClave (I can't speak to the challenges faced by VR on the blockchain- that sounds intense!). The Ethereum community is constantly rolling out updates that address load and scaling issues, so keeping our code up to date and in sync with the latest Ethereum updates is key. We are also working with other blockchain providers to see if there is a potential for a partnership where we could have tighter integration to address unique BitClave user load challenges, though this is a future challenge.

Ok, so whether or not the desired goal will be fully achievable remains to be seen for now I guess? I mean, I do think that at some point in time in the future close to unlimited scalability might be a possibility. I think Vitalik is already dealing with something like that. We'll see how turns out.