TimeKoin Forums

I don't post a lot on social media or about personal or family matters publicly, but I want everyone to know that my absence is only to deal with these recent personal family tragedy(s). It takes a lot personal time, along with my work obligations (some of which are Timekoin related) so it just does...

warmach wrote: ↑Thu Sep 09, 2021 3:22 pm OK, it is back....now what?

Sorry, with so many "social" areas to check, I only have so much time to reply to them all.

Working on getting it to exchanges, private entities, etc. Getting the word out on the merits and uses for it.

If you are running the all-in-one windows server exe version 4.14 or lower, there is a 32 bit number field that should have been upgraded to a 64 bit number field a while back when those server packages were being created. To be more specific, the table "main_loop_status" should have a 64 ...

Probably a while, with so many places to communicate (other forums, discord, etc.) It will take some time for people to find their way back.

collapse wrote:My version of server supporting PostgreSQL, (now under test).
https://github.com/inetarius/inetarius/tree/timekoin

Cool, excellent! You should make a topic just for this, so it isn't buried in all the other discussion here.

Can you please include a way to use easy key to populate the public key field? This is already possible. Just write your Easy key and click on the Easy Key button and the public key field will be populated. Sorry I didn't explain that more clearly. I was referring to the TX Explorer on Timekoin.org...

Yes, those 4097 duplicates can come about because only transactions need unique SHA256 outputs per transaction, but the SHA256 of a transaction cycle could be the same if the data being put into the SHA256 hash was identical/similar enough to somewhere else in the past. It is also known that when cr...

This is exactly what I want to do... No different than some of the browser based wallets available now. You need to trust the server. Unless, and this is just crazy talk, would there be a way to create one time use keys? You sure can, if you can generate a RSA key pair, it only needs to be 1,536 bi...

This is exactly what I want to do... No different than some of the browser based wallets available now. You need to trust the server. Unless, and this is just crazy talk, would there be a way to create one time use keys? You sure can, if you can generate a RSA key pair, it only needs to be 1,536 bi...

I guess this leads me to the next question, do I even need to do the crypto side of it in Pythong? Shouldn't the API handle all that? Right now, the api call to send TK requires that I do the hashing and encrypting before sending it to the server. Why couldn't there be an API call that you provide ...