[ANN][SMC] SmartCoin | Next generation currency | continued development - page 3.

psionin

sr. member

Activity: 465

Merit: 254

I don't see Komodo being used much and DEXs now seem to have mostly Ethereum token trades but not the main cryptos.

https://np.reddit.com/r/Monero/comments/i1fknt/ccs_results_monero_atomic_swaps_research/

Still more theoretical discussion about how swaps should work, it doesn't seem to have been solved yet properly.

I was thinking about interfacing with regular exchanges for now to get coins for withdrawal or to provide liquidity for certain pairs. Of course a better DEX solution would be more optimal though.

Quote from: readyUP on July 29, 2020, 08:59:42 AM

Quote from: psionin on July 28, 2020, 11:34:51 AM

Let me know what kind of DEX you are thinking about, if there are any examples in particular.

I thought DEX as BlockNet, or Komodo's AtomicDex. there is also that of the blockchain of Burst but I don't know how it is.

readyUP

newbie

Activity: 182

Merit: 0

Quote from: psionin on July 28, 2020, 11:34:51 AM

Let me know what kind of DEX you are thinking about, if there are any examples in particular.

I thought DEX as BlockNet, or Komodo's AtomicDex. there is also that of the blockchain of Burst but I don't know how it is.

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: psionin on July 28, 2020, 11:51:57 PM

I agree here, I've also thought about it before and don't care for making some dubious hacked exchange account rich, especially while they contribute nothing and do not engage at all with the community. We'll have to see about what kind of a solution would make sense, maybe a vote perhaps. It's good to have this discussion.

One approach is to edit the UTXO to exclude the offending addy and reassign the balance to a community-owned multi-sig address for use thereafter as a community Treasury.

Cheers

Graham

psionin

sr. member

Activity: 465

Merit: 254

I agree here, I've also thought about it before and don't care for making some dubious hacked exchange account rich, especially while they contribute nothing and do not engage at all with the community. We'll have to see about what kind of a solution would make sense, maybe a vote perhaps. It's good to have this discussion.

We can chat here for now, but after the fork and some exchange listings, if the community grows, we can move to other platforms as well. This is still the place that is most responsive for now.

Quote from: jdmcg on July 28, 2020, 03:59:14 PM

Quote from: psionin on July 28, 2020, 11:26:29 AM

Then maybe. Does that mean that the address that it went to should be invalidated? What if it was already sold several times and the other parties paid legitimately for it? Or should new ones be generated to replace the loss at the expense of the whole network? What about cases when it was lost like Bitcoin in old hard drives?

Complicated topic here, I don't want to say yes or no. But my question is, even if it is a million SMC, is it such a big deal? It's basically worthless now. I would just buy another batch and keep it safe off the exchange this time if it's a project that I believed in and it was important to me.

Quote from: jdmcg on July 27, 2020, 03:38:52 PM

Quote from: psionin on July 27, 2020, 12:56:23 AM

In regard to the claims from Cryptsy, I don't see a way to reverse it, does anyone else have a proposal? Can't just issue replacements for anyone who makes a claim without proof.

And if they have proof?

Seems to me the majority of Cryptsy's SMC ended up at SY9JewNadnkJexXxLKfmFhqoaeQycTVDS6, 4,420,304.00000000 ended up there end of Jan 2018. I would think regardless what you decide this balance should be excluded from any kind of swap. Someone obviously still had control of these stolen coins as they had moved them periodically from 2016 to beginning of 2018.

If you would honor such claims with proof I would just think the total claims couldn't exceed this balance. Regarding lost wallets (from lost hard drives and such), I don't see this as being the same. Not only almost impossible to prove but no crime was likely committed.

Now if I were to try to re-buy all the cryptos stolen from me over the last 6 years or so from all the various exchanges, it would be a small fortune.

Is there a better place than here to get an opinion on this? Would be nice to get others commenting whether for or against. Thanks.

jdmcg

member

Activity: 264

Merit: 22

Quote from: psionin on July 28, 2020, 11:26:29 AM

Then maybe. Does that mean that the address that it went to should be invalidated? What if it was already sold several times and the other parties paid legitimately for it? Or should new ones be generated to replace the loss at the expense of the whole network? What about cases when it was lost like Bitcoin in old hard drives?

Complicated topic here, I don't want to say yes or no. But my question is, even if it is a million SMC, is it such a big deal? It's basically worthless now. I would just buy another batch and keep it safe off the exchange this time if it's a project that I believed in and it was important to me.

Quote from: jdmcg on July 27, 2020, 03:38:52 PM

Quote from: psionin on July 27, 2020, 12:56:23 AM

In regard to the claims from Cryptsy, I don't see a way to reverse it, does anyone else have a proposal? Can't just issue replacements for anyone who makes a claim without proof.

And if they have proof?

Seems to me the majority of Cryptsy's SMC ended up at SY9JewNadnkJexXxLKfmFhqoaeQycTVDS6, 4,420,304.00000000 ended up there end of Jan 2018. I would think regardless what you decide this balance should be excluded from any kind of swap. Someone obviously still had control of these stolen coins as they had moved them periodically from 2016 to beginning of 2018.

If you would honor such claims with proof I would just think the total claims couldn't exceed this balance. Regarding lost wallets (from lost hard drives and such), I don't see this as being the same. Not only almost impossible to prove but no crime was likely committed.

Now if I were to try to re-buy all the cryptos stolen from me over the last 6 years or so from all the various exchanges, it would be a small fortune.

Is there a better place than here to get an opinion on this? Would be nice to get others commenting whether for or against. Thanks.

psionin

sr. member

Activity: 465

Merit: 254

It wouldn't be a swap, the keys should be importable into the new wallet without any hassle.

I made a Telegram chat but there hasn't been enough interest in it. Maybe later on it can pick up.

Let me know what kind of DEX you are thinking about, if there are any examples in particular.

Quote from: readyUP on July 27, 2020, 10:04:38 AM

Hello, it's really nice to see such a dated project being still active and wanting to get back on track ..
The site is simple, minimal but it is done well.
It is not the usual site that inspires a scam. How blockchain updates will happen.
With a simple swap?
If it were active in more DEX I think it would be better.
Are you going to open new social channels, maybe Talegram and Discord ?!
I look forward to news, perhaps with an unofficial roadmap.
Thanks for your time.

psionin

sr. member

Activity: 465

Merit: 254

Then maybe. Does that mean that the address that it went to should be invalidated? What if it was already sold several times and the other parties paid legitimately for it? Or should new ones be generated to replace the loss at the expense of the whole network? What about cases when it was lost like Bitcoin in old hard drives?

Complicated topic here, I don't want to say yes or no. But my question is, even if it is a million SMC, is it such a big deal? It's basically worthless now. I would just buy another batch and keep it safe off the exchange this time if it's a project that I believed in and it was important to me.

Quote from: jdmcg on July 27, 2020, 03:38:52 PM

Quote from: psionin on July 27, 2020, 12:56:23 AM

In regard to the claims from Cryptsy, I don't see a way to reverse it, does anyone else have a proposal? Can't just issue replacements for anyone who makes a claim without proof.

And if they have proof?

jdmcg

member

Activity: 264

Merit: 22

Quote from: psionin on July 27, 2020, 12:56:23 AM

In regard to the claims from Cryptsy, I don't see a way to reverse it, does anyone else have a proposal? Can't just issue replacements for anyone who makes a claim without proof.

And if they have proof?

readyUP

newbie

Activity: 182

Merit: 0

Hello, it's really nice to see such a dated project being still active and wanting to get back on track ..
The site is simple, minimal but it is done well.
It is not the usual site that inspires a scam. How blockchain updates will happen.
With a simple swap?
If it were active in more DEX I think it would be better.
Are you going to open new social channels, maybe Talegram and Discord ?!
I look forward to news, perhaps with an unofficial roadmap.
Thanks for your time.

psionin

sr. member

Activity: 465

Merit: 254

There are a number of things happening and if they go through successfully then I think the SMC evolution can be part of it. For me it's not only about making an update to the blockchain but also having an application for this specific coin also.

I spent some time looking at CryptoNote, maybe it should have a layer of anonymity, and then a decentralized exchange aspect to it like with Komodo. A lot of complicated things to rework if doing it in C++. I was hoping to get away with using Python as much as possible. Not sure about NEM, I would rather not be getting into Java.

In regard to the claims from Cryptsy, I don't see a way to reverse it, does anyone else have a proposal? Can't just issue replacements for anyone who makes a claim without proof. However, it does seem like the majority of coins are sitting in some wallet with the entity controlling it never contributing anything to the project at all. If they were bought legitimately, then that's fine I suppose. But if it's through some criminal enterprise that hacks exchanges and gets the funds from them that way (Cryptsy, Cryptopia) while the actual owners lose them, then that is not good. However, unfortunately, I don't have a solution. Any ideas or other feedback on this?

Quote from: jdmcg on July 15, 2020, 11:12:31 AM

Are you still planning to fork over to a new blockchain? If so will you do an opt in like NEM? And would you consider claims from those who lost SMC from scam exchanges like Cryptsy?

jdmcg

member

Activity: 264

Merit: 22

Are you still planning to fork over to a new blockchain? If so will you do an opt in like NEM? And would you consider claims from those who lost SMC from scam exchanges like Cryptsy?

Bootheman

jr. member

Activity: 34

Merit: 7

Make it rain! Grin

four3200

sr. member

Activity: 1246

Merit: 257

Quote from: notsofast on May 29, 2020, 11:43:20 AM

Fantastic to see this network making a comeback!

I'm having some trouble finding peers. Could anyone please post an updated node list?

Edit: nevermind, found a couple peers

Code:

addnode=95.183.50.2:58585
addnode=178.63.9.83:58585

Hope it does. Honest decent project since 2014.

psionin

sr. member

Activity: 465

Merit: 254

Agreed, and also update the website, make a new explorer, update the code, release Electrum, add to more exchanges, etc..

Been getting a bit distracted recently.

Quote from: fonship on June 02, 2020, 10:15:35 PM

You should really update the announcement thread

fonship

full member

Activity: 893

Merit: 135

Bitcoin is not a currency or asset. Its a MOVEMENT

You should really update the announcement thread

psionin

sr. member

Activity: 465

Merit: 254

Yeah I'm not sure where to post updates, I guess here is fine for now. Maybe a bit later in a blog.

So far so good in the past couple of weeks, it's easier to make changes than before, after lots of learning in the prior years.

One of the issues now is that it gets mined on and off for 3 days at a time, and when it's off there isn't even a single Baikal Giant mining, and transactions don't go through for a while. This would get resolved if there is more usage and demand for it, which I guess would be more likely if it is upgraded. So doing the node update to a later version of Litecoin is the priority now (then a new block explorer with better stats, online wallet/tipbot, Electrum server and wallet with Trezor support).

If it all goes well then it would be a nice milestone to get through. Afterwards, maybe a privacy layer, but also DEX, and a better mining system. That is the more challenging part, the fork after the more basic upgrade. Lots of ideas for it.

Quote from: notsofast on May 29, 2020, 11:43:20 AM

Fantastic to see this network making a comeback!

I'm having some trouble finding peers. Could anyone please post an updated node list?

Edit: nevermind, found a couple peers

Code:

addnode=95.183.50.2:58585
addnode=178.63.9.83:58585

notsofast

legendary

Activity: 1517

Merit: 1042

@notsofast

Fantastic to see this network making a comeback!

I'm having some trouble finding peers. Could anyone please post an updated node list?

Edit: nevermind, found a couple peers

Code:

addnode=95.183.50.2:58585
addnode=178.63.9.83:58585

psionin

sr. member

Activity: 465

Merit: 254

Making progress with Electrum...

Code:

-- Logs begin at Sun 2020-05-24 20:00:11 MSK. --
May 25 11:37:40 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 9 daemon: 2,832,183 UTXOs 0MB hist 0MB
May 25 11:38:10 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 89,009 daemon: 2,832,183 UTXOs 20MB hist 43MB
May 25 11:38:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 150,609 daemon: 2,832,183 UTXOs 23MB hist 53MB
May 25 11:39:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 185,409 daemon: 2,832,183 UTXOs 24MB hist 58MB
May 25 11:39:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 217,609 daemon: 2,832,183 UTXOs 27MB hist 62MB
May 25 11:40:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 251,109 daemon: 2,832,183 UTXOs 30MB hist 67MB
May 25 11:40:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 280,809 daemon: 2,832,183 UTXOs 31MB hist 72MB
May 25 11:41:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 316,109 daemon: 2,832,183 UTXOs 33MB hist 77MB
May 25 11:41:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 354,109 daemon: 2,832,183 UTXOs 35MB hist 83MB
May 25 11:42:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 391,509 daemon: 2,832,183 UTXOs 37MB hist 88MB
May 25 11:42:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 426,209 daemon: 2,832,183 UTXOs 40MB hist 93MB
May 25 11:43:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 471,609 daemon: 2,832,183 UTXOs 44MB hist 98MB
May 25 11:43:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 518,109 daemon: 2,832,183 UTXOs 51MB hist 103MB
May 25 11:44:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 560,209 daemon: 2,832,183 UTXOs 56MB hist 108MB
May 25 11:44:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 598,109 daemon: 2,832,183 UTXOs 62MB hist 112MB
May 25 11:45:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 639,809 daemon: 2,832,183 UTXOs 65MB hist 116MB
May 25 11:45:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 687,109 daemon: 2,832,183 UTXOs 66MB hist 120MB
May 25 11:46:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 728,809 daemon: 2,832,183 UTXOs 54MB hist 124MB
May 25 11:46:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 765,409 daemon: 2,832,183 UTXOs 56MB hist 127MB
May 25 11:47:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 801,409 daemon: 2,832,183 UTXOs 57MB hist 131MB
May 25 11:47:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 846,209 daemon: 2,832,183 UTXOs 52MB hist 135MB
May 25 11:48:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 895,109 daemon: 2,832,183 UTXOs 46MB hist 140MB
May 25 11:48:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 942,209 daemon: 2,832,183 UTXOs 46MB hist 144MB
May 25 11:49:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 991,109 daemon: 2,832,183 UTXOs 47MB hist 150MB
May 25 11:49:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,038,309 daemon: 2,832,183 UTXOs 49MB hist 155MB
May 25 11:50:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,079,709 daemon: 2,832,183 UTXOs 50MB hist 159MB
May 25 11:50:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,126,509 daemon: 2,832,183 UTXOs 52MB hist 163MB
May 25 11:51:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,163,609 daemon: 2,832,183 UTXOs 53MB hist 167MB
May 25 11:51:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,198,009 daemon: 2,832,183 UTXOs 46MB hist 170MB
May 25 11:52:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,228,709 daemon: 2,832,183 UTXOs 46MB hist 172MB
May 25 11:52:41 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,260,609 daemon: 2,832,183 UTXOs 46MB hist 175MB
May 25 11:53:11 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,291,609 daemon: 2,832,183 UTXOs 48MB hist 177MB
May 25 11:53:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,323,209 daemon: 2,832,183 UTXOs 48MB hist 180MB
May 25 11:54:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,353,509 daemon: 2,832,183 UTXOs 50MB hist 182MB
May 25 11:54:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,384,009 daemon: 2,832,183 UTXOs 51MB hist 185MB
May 25 11:55:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,413,709 daemon: 2,832,183 UTXOs 51MB hist 188MB
May 25 11:55:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,442,909 daemon: 2,832,183 UTXOs 50MB hist 190MB
May 25 11:56:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,472,209 daemon: 2,832,183 UTXOs 50MB hist 193MB
May 25 11:56:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,501,209 daemon: 2,832,183 UTXOs 53MB hist 195MB
May 25 11:57:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,530,109 daemon: 2,832,183 UTXOs 54MB hist 197MB
May 25 11:57:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,559,309 daemon: 2,832,183 UTXOs 51MB hist 200MB
May 25 11:58:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,588,509 daemon: 2,832,183 UTXOs 57MB hist 202MB
May 25 11:58:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,617,109 daemon: 2,832,183 UTXOs 51MB hist 205MB
May 25 11:59:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,646,009 daemon: 2,832,183 UTXOs 51MB hist 207MB
May 25 11:59:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,675,009 daemon: 2,832,183 UTXOs 57MB hist 210MB
May 25 12:00:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,703,709 daemon: 2,832,183 UTXOs 53MB hist 212MB
May 25 12:00:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,732,709 daemon: 2,832,183 UTXOs 53MB hist 215MB
May 25 12:01:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,761,709 daemon: 2,832,183 UTXOs 53MB hist 217MB
May 25 12:01:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,790,609 daemon: 2,832,183 UTXOs 49MB hist 220MB
May 25 12:02:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,819,709 daemon: 2,832,183 UTXOs 55MB hist 222MB
May 25 12:02:42 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,848,409 daemon: 2,832,183 UTXOs 51MB hist 225MB
May 25 12:03:12 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,877,509 daemon: 2,832,183 UTXOs 57MB hist 227MB
May 25 12:03:43 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,906,609 daemon: 2,832,183 UTXOs 63MB hist 230MB
May 25 12:04:13 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,935,109 daemon: 2,832,183 UTXOs 52MB hist 233MB
May 25 12:04:43 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 1,964,209 daemon: 2,832,183 UTXOs 58MB hist 235MB
May 25 12:05:13 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,000,309 daemon: 2,832,183 UTXOs 60MB hist 238MB
May 25 12:05:43 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,035,609 daemon: 2,832,183 UTXOs 60MB hist 241MB
May 25 12:05:43 debian electrumx_server[6462]: INFO:DB:flushed filesystem data in 0.43s
May 25 12:05:44 debian electrumx_server[6462]: INFO:History:flushed history in 0.6s for 353,703 addrs
May 25 12:05:44 debian electrumx_server[6462]: INFO:DB:flush #1 took 1.3s. Height 2,035,609 txs: 2,363,515 (+2,363,515)
May 25 12:05:44 debian electrumx_server[6462]: INFO:DB:tx/sec since genesis: 1,403, since last flush: 1,404
May 25 12:05:44 debian electrumx_server[6462]: INFO:DB:sync time: 28m 04s ETA: 10m 15s
May 25 12:06:14 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,066,709 daemon: 2,832,183 UTXOs 56MB hist 2MB
May 25 12:06:44 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,096,309 daemon: 2,832,183 UTXOs 54MB hist 5MB
May 25 12:07:14 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,125,609 daemon: 2,832,183 UTXOs 60MB hist 7MB
May 25 12:07:44 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,154,809 daemon: 2,832,183 UTXOs 66MB hist 10MB
May 25 12:08:14 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,184,009 daemon: 2,832,183 UTXOs 72MB hist 12MB
May 25 12:08:44 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,211,771 daemon: 2,832,183 UTXOs 50MB hist 15MB
May 25 12:09:14 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,241,171 daemon: 2,832,183 UTXOs 56MB hist 17MB
May 25 12:09:44 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,270,371 daemon: 2,832,183 UTXOs 62MB hist 19MB
May 25 12:10:14 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,298,968 daemon: 2,832,183 UTXOs 53MB hist 22MB
May 25 12:10:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,328,268 daemon: 2,832,183 UTXOs 59MB hist 24MB
May 25 12:11:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,357,368 daemon: 2,832,183 UTXOs 65MB hist 26MB
May 25 12:11:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,386,668 daemon: 2,832,183 UTXOs 71MB hist 29MB
May 25 12:12:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,415,768 daemon: 2,832,183 UTXOs 77MB hist 31MB
May 25 12:12:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,445,068 daemon: 2,832,183 UTXOs 83MB hist 33MB
May 25 12:13:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,472,219 daemon: 2,832,183 UTXOs 49MB hist 36MB
May 25 12:13:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,501,319 daemon: 2,832,183 UTXOs 55MB hist 38MB
May 25 12:14:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,530,619 daemon: 2,832,183 UTXOs 61MB hist 40MB
May 25 12:14:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,559,819 daemon: 2,832,183 UTXOs 67MB hist 43MB
May 25 12:15:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,589,019 daemon: 2,832,183 UTXOs 73MB hist 45MB
May 25 12:15:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,618,319 daemon: 2,832,183 UTXOs 79MB hist 47MB
May 25 12:16:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,651,819 daemon: 2,832,183 UTXOs 73MB hist 50MB
May 25 12:16:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,681,419 daemon: 2,832,183 UTXOs 52MB hist 53MB
May 25 12:17:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,710,719 daemon: 2,832,183 UTXOs 58MB hist 56MB
May 25 12:17:45 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,739,919 daemon: 2,832,183 UTXOs 64MB hist 58MB
May 25 12:18:15 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,769,119 daemon: 2,832,183 UTXOs 70MB hist 60MB
May 25 12:18:46 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,798,319 daemon: 2,832,183 UTXOs 76MB hist 62MB
May 25 12:19:16 debian electrumx_server[6462]: INFO:BlockProcessor:our height: 2,825,875 daemon: 2,832,183 UTXOs 49MB hist 65MB
May 25 12:19:21 debian electrumx_server[6462]: INFO:BlockProcessor:caught up to height 2832183
May 25 12:19:22 debian electrumx_server[6462]: INFO:DB:flushed filesystem data in 0.13s
May 25 12:19:22 debian electrumx_server[6462]: INFO:History:flushed history in 0.1s for 17,515 addrs
May 25 12:19:22 debian electrumx_server[6462]: INFO:DB:flushed 2,832,184 blocks with 3,169,313 txs, 234,320 UTXO adds, 0 spends in 0.2s, committing...
May 25 12:19:22 debian electrumx_server[6462]: INFO:DB:flush #2 took 0.8s. Height 2,832,183 txs: 3,169,313 (+805,798)
May 25 12:19:22 debian electrumx_server[6462]: INFO:DB:tx/sec since genesis: 1,266, since last flush: 985
May 25 12:19:22 debian electrumx_server[6462]: INFO:DB:sync time: 41m 42s ETA: 00s
May 25 12:19:22 debian electrumx_server[6462]: INFO:BlockProcessor:ElectrumX 1.14.0 synced to height 2,832,183
May 25 12:19:22 debian electrumx_server[6462]: INFO:DB:closing DBs to re-open for serving
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:opened UTXO DB (for sync: False)
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:UTXO DB version: 8
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:coin: Smartcoin
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:network: mainnet
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:height: 2,832,183
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:tip: dc65249450775522af87b0af947d05730b6b39b6f1a4e2b795629189a443a715
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:tx count: 3,169,313
May 25 12:19:23 debian electrumx_server[6462]: INFO:History:history DB version: 1
May 25 12:19:23 debian electrumx_server[6462]: INFO:History:flush count: 2
May 25 12:19:23 debian electrumx_server[6462]: INFO:DB:populating header merkle cache...
May 25 12:19:23 debian electrumx_server[6462]: INFO:MemPool:beginning processing of daemon mempool. This can take some time...
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:max session count: 1,000
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:session timeout: 600 seconds
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:session cost hard limit 10,000
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:session cost soft limit 1,000
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:bandwidth unit cost 5,000
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:request sleep 2,500ms
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:request timeout 30s
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:initial concurrent 10
May 25 12:19:23 debian electrumx_server[6462]: INFO:SessionManager:max response size 1,000,000 bytes
May 25 12:19:23 debian electrumx_server[6462]: INFO:MemPool:synced in 0.00s
May 25 12:19:23 debian electrumx_server[6462]: INFO:MemPool:0 txs 0.00 MB touching 0 addresses
May 25 12:19:23 debian electrumx_server[6462]: INFO:MemPool:compact fee histogram: []
May 25 12:19:23 debian electrumx_server[6462]: INFO:PeerManager:peer discovery: ON
May 25 12:19:23 debian electrumx_server[6462]: INFO:PeerManager:announce ourself: True
May 25 12:19:23 debian electrumx_server[6462]: INFO:PeerManager:my clearnet self: None
May 25 12:19:23 debian electrumx_server[6462]: INFO:PeerManager:force use of proxy: False
May 25 12:19:23 debian electrumx_server[6462]: INFO:PeerManager:beginning peer discovery...
May 25 12:19:23 debian electrumx_server[6462]: INFO:PeerManager:trying to detect proxy on "localhost" ports [9050, 9150, 1080]
May 25 12:19:24 debian electrumx_server[6462]: INFO:PeerManager:no proxy detected, will try later
May 25 12:19:33 debian electrumx_server[6462]: INFO:DB:header merkle cache populated in 9.3s
May 25 12:20:28 debian electrumx_server[6462]: INFO:MemPool:0 txs 0.00 MB touching 0 addresses
May 25 12:21:28 debian electrumx_server[6462]: INFO:MemPool:0 txs 0.00 MB touching 0 addresses
May 25 12:22:28 debian electrumx_server[6462]: INFO:MemPool:0 txs 0.00 MB touching 0 addresses

Code:

{
"coin": "Smartcoin",
"daemon": "127.0.0.1:8583/",
"daemon height": 2832183,
"db height": 2832183,
"db_flush_count": 2,
"groups": 2,
"history cache": "0 lookups 0 hits 0 entries",
"merkle cache": "0 lookups 0 hits 0 entries",
"peers": {
"bad": 0,
"good": 0,
"never": 0,
"stale": 0,
"total": 0
},
"pid": 9698,
"request counts": {
"getinfo": 1
},
"request total": 1,
"sessions": {
"count": 1,
"count with subs": 0,
"errors": 0,
"logged": 0,
"pending requests": 1,
"subs": 0
},
"tx hashes cache": "0 lookups 0 hits 0 entries",
"txs sent": 0,
"uptime": "47s",
"version": "ElectrumX 1.14.0"
}

psionin

sr. member

Activity: 465

Merit: 254

Quote from: Bootheman on May 22, 2020, 09:05:46 PM

Interesting spike in trades over the past week, any further insight into the updates? Thanks

Some bot, I think, not really anything spectacular.

I do have an update though, started to get back to SmartCoin recently.

Need to get the code updated to a recent version of the Bitcoin protocol so that it builds easier on more recent systems (I built it on Debian 10 just now but it wasn't trivial). Yobit has the wallet in maintenance, this should make it easier for them to resolve the issue.

Also want to get the Electrum wallet out so that transactions can be made without downloading the blockchain.

Then it would be time to fork to a different mining process, and once that is successful, we can go ahead and add it to more exchanges.

There is also the decentralized exchange aspect that may be associated with this fork.

That's it for now.

psionin

Bootheman

jr. member

Activity: 34

Merit: 7

Interesting spike in trades over the past week, any further insight into the updates? Thanks

Topic: [ANN][SMC] SmartCoin | Next generation currency | continued development - page 3. (Read 157120 times)