[ANN] [XJO] Joulecoin | SHA256 | First SHA256 data coin | Major upgrade 0.10.4.2 - page 11.

dalslandan200

newbie

Activity: 30

Merit: 0

Quote from: shinohai on October 11, 2018, 09:14:53 AM

I have applied a couple of fixes to XJO sources, but for some reason shithub won't let me make pull request to main repo, as it hates when you have multiple sources of same project. This is mostly a simple change I applied because C++11 doesn't play nice with the main repo for whatever reason:

https://github.com/Shinoa-Fores/joulecoin/commit/c2983f8d6a74fca82a7581dd34275e869d17a94c
and
https://github.com/Shinoa-Fores/joulecoin/commit/18116e0a6f436079fa9ee9f0b67b697d2beb292a (Because I forgot to push it the first day xD )

One or two other minor fixes listed there that may or may not affect others, I use Gentoo so these may not be a problem on other distros, haven't tested yet.

I use CentOS 7, and have used Ubuntu before.
I haven't had this issue at all, and recompiled to check again.

I know I have somewhat been in contact with the issue before, but I can't remember thoroughly where.

Newer version of Bitcoin source code have changed to full path, so probably others have encountered the same issue.

By the way, if you wanna talk more interactively you can join the Joulecoin Discord channel: https://discord.gg/RaWB3uE
And send me a private message.

shinohai

full member

Activity: 267

Merit: 109

Quote from: dalslandan200 on October 10, 2018, 08:33:34 PM

Quote from: shinohai on October 07, 2018, 10:56:27 AM

This is awesum work as well! Feel free to message if I can be of any assistance, having insight API is a very important thing for developers. Already have a couple of ideas brewin and look forward to having the tx comments enabled. I have a bot skeleton on telegram that could definitely make use of this.

Finished up with the API and added some visual preferences, e.g. the arrow turns "blue" when there is a transaction message available; simply click on the transaction ID, and the message is there with all the other information.

Here you can witness one of the first comments ever used: https://insight.joulecoin.info/block/000000000017ec018cc65d56d69d737f9da00b885c69a207b1b1219728502cdf

The API is available on: https://insight.joulecoin.info/api

I hope everyone using it will take it easy on my free services.

Top notch work! I let IMZ know this was up, and I will likely use the API on my telegram bot, as I mentioned previously (But don't worry, abusers of bot services quickly get blacklisted and in our small group everyone s well behaved

).

I have applied a couple of fixes to XJO sources, but for some reason shithub won't let me make pull request to main repo, as it hates when you have multiple sources of same project. This is mostly a simple change I applied because C++11 doesn't play nice with the main repo for whatever reason:

https://github.com/Shinoa-Fores/joulecoin/commit/c2983f8d6a74fca82a7581dd34275e869d17a94c
and
https://github.com/Shinoa-Fores/joulecoin/commit/18116e0a6f436079fa9ee9f0b67b697d2beb292a (Because I forgot to push it the first day xD )

One or two other minor fixes listed there that may or may not affect others, I use Gentoo so these may not be a problem on other distros, haven't tested yet.

dalslandan200

newbie

Activity: 30

Merit: 0

Quote from: shinohai on October 07, 2018, 10:56:27 AM

This is awesum work as well! Feel free to message if I can be of any assistance, having insight API is a very important thing for developers. Already have a couple of ideas brewin and look forward to having the tx comments enabled. I have a bot skeleton on telegram that could definitely make use of this.

Finished up with the API and added some visual preferences, e.g. the arrow turns "blue" when there is a transaction message available; simply click on the transaction ID, and the message is there with all the other information.

Here you can witness one of the first comments ever used: https://insight.joulecoin.info/block/000000000017ec018cc65d56d69d737f9da00b885c69a207b1b1219728502cdf

The API is available on: https://insight.joulecoin.info/api

I hope everyone using it will take it easy on my free services.

shinohai

full member

Activity: 267

Merit: 109

Quote from: dalslandan200 on October 07, 2018, 12:34:30 AM

Have been busy the last 2 weeks integrating Joulecoin into all insight libraries, and modifying the Bitcore client.

After a lot of headaches I finally got it up and running, and have the last few days done some visual improvements.

I'm planning to upload everything organized to GitHub, once I have cleaned it up more and fixed some other remaining things.

Unfortunately I have not completely integrated transaction messages into the API.
I know, but it will be fixed soon.

It is far from complete (if it ever will be), but I feel I'm comfortable having it online now.

For anyone wanting to take a look,
Introducing: https://insight.joulecoin.info/

This is awesum work as well! Feel free to message if I can be of any assistance, having insight API is a very important thing for developers. Already have a couple of ideas brewin and look forward to having the tx comments enabled. I have a bot skeleton on telegram that could definitely make use of this.

dalslandan200

newbie

Activity: 30

Merit: 0

Quote from: shinohai on October 05, 2018, 10:41:39 PM

Quote from: IMZ Noo Account on September 29, 2018, 07:30:31 PM

One of our guys made me a 'paper wallet' to sweep. Excellent!!

Joulecoin paper wallet generator now available at: http://btcinfo.sdf.org/DLX/genwallet/?currency=joulecoin#

Source code on my github: https://github.com/Shinoa-Fores/WalletGenerator.net

I created a pull request in an effort to get it officially added to WalletGenerator.net - will update when/if that happens.

Was going to look into paper-wallets as well.
Good initiative.

Have been busy the last 2 weeks integrating Joulecoin into all insight libraries, and modifying the Bitcore client.

After a lot of headaches I finally got it up and running, and have the last few days done some visual improvements.

I'm planning to upload everything organized to GitHub, once I have cleaned it up more and fixed some other remaining things.

Unfortunately I have not completely integrated transaction messages into the API.
I know, but it will be fixed soon.

It is far from complete (if it ever will be), but I feel I'm comfortable having it online now.

For anyone wanting to take a look,
Introducing: https://insight.joulecoin.info/

shinohai

full member

Activity: 267

Merit: 109

Quote from: IMZ Noo Account on September 29, 2018, 07:30:31 PM

One of our guys made me a 'paper wallet' to sweep. Excellent!!

Joulecoin paper wallet generator now available at: http://btcinfo.sdf.org/DLX/genwallet/?currency=joulecoin#

Source code on my github: https://github.com/Shinoa-Fores/WalletGenerator.net

I created a pull request in an effort to get it officially added to WalletGenerator.net - will update when/if that happens.

IMZ Noo Account

member

Activity: 746

Merit: 26

Yup. We are developing XJO. My outfit has a bunker on Telegram

Wanna do p2p trades!!!!

IMZ Noo Account

member

Activity: 746

Merit: 26

One of our guys made me a 'paper wallet' to sweep. Excellent!!

ComputerGenie

hero member

Activity: 1092

Merit: 552

Retired IRCX God

Quote from: ?? on ??

--- Reserved ---

On page 64? Now there's the dumbest thing I've ever seen happen on this forum. Undecided

lokkytan

jr. member

Activity: 74

Merit: 1

Look ARROUND!

Quote from: dalslandan200 on September 13, 2018, 08:08:15 AM

Quote from: Introvard on September 13, 2018, 05:32:36 AM

>>Block reward: 16 XJO

When solo decoding a block, I get 4 xjo instead of 16 xjo. Why? Undecided

Because of how halving works to prolong the "original" mining phase.
Like many altcoins, Joulecoin implements the halving technique to more slowly reach the total supply of issued coins (~ 45 million XJO).
We are currently in our second halving stage which results in a XJO reward of 4 instead of 8 or 16.

According to Joulecoin configuration, halving occurs every 2 years.

So, roughly 2 * (31 556 926 / 45) approx. 1 402 530 (this means that approximately block 1 402 530 should have the new block-award since 2 years have passed, but if the chain have had issues this could be longer or shorter)

If we look at Block explorer at around 1 400 000 (https://chainz.cryptoid.info/xjo/block.dws?000000000000f6256c21d60466bc9b7aab1704f5681e504546d1e9ca48074d9e.htm)
We can see that there still is the original 16 XJO reward.

So, let's calculate where 4 XJO happens. (4 * (31 556 926 / 45) approx. 2 805 060)

If we look at Block explorer again, but at 2 800 000 (https://chainz.cryptoid.info/xjo/block.dws?0000000000001561b85d4dde5aa9ada2fc491fbb1cee8fca9148df0f3e2d48b7.htm)
We can see that the 8 XJO reward is currently in place.

But if we check at block 2 805 060 (https://chainz.cryptoid.info/xjo/block.dws?0000000000000b807131df697a91d769f950b0aa04b4cd6cc09d7c50928d929b.htm)
We can confirm that the 4 XJO reward have indeed started occurring.

Disclaimer: I know this math is not preferred*

oh great, there are many things to be learned here, the project is developing and progressing will be a quality project with a lot of support from the community.

IMZ Noo Account

member

Activity: 746

Merit: 26

Quote from: dalslandan200 on September 11, 2018, 12:32:03 AM

Quote from: IMZ Noo Account on September 09, 2018, 11:07:31 PM

We are getting better:

encrypt a message. Run it through a paste bin. Send the URL as a tx comment.

Made a web page where it is possible to encrypt a message via AES encryption with a key.

The compression ratio isn't perfect, but it increases to 67.4% before 240 character limit is reached.

However website linking is an awesome way to save storage for the Blockchain.

I got the following number for efficiency on the encryption compression ratio:

Code:

0.341 IN:15 OUT:44
0.484 IN:31 OUT:64
0.583 IN:63 OUT:108
0.617 IN:79 OUT:128
0.625 IN:95 OUT:152
0.645 IN:111 OUT:172
0.662 IN:143 OUT:216
0.674 IN:159 OUT:236

So at a small encryption it is around 35%, going all the way to ~67% at its best (maximum length encryption).
Which provides an maximum input of 159 characters before encryption, resulting in a 236 character long hash.

It's made possible with Javascript, so everything is happening local.
GitHub: https://github.com/brix/crypto-js/tree/release-3.1.2

I haven't made the first encrypted transaction message via the website yet.
Probably will later.

I had issues making clipboard button cross-browser compatibility with legacy support. So I have not missed this, I just wasn't happy with the current outcome.
Regarding the possibility to download the web page and run on other machines which are not connected to the internet, is also something I have in the pipeline.

Introducing: https://joulecoin.info/encrypt.html
- Online AES encryption and decryption made in mind for Joulecoin transaction comments.

Oh wow! So much here that I need to learn! So cool to see this project advancing.

dalslandan200

newbie

Activity: 30

Merit: 0

Quote from: Introvard on September 13, 2018, 05:32:36 AM

>>Block reward: 16 XJO

When solo decoding a block, I get 4 xjo instead of 16 xjo. Why? Undecided

Because of how halving works to prolong the "original" mining phase.
Like many altcoins, Joulecoin implements the halving technique to more slowly reach the total supply of issued coins (~ 45 million XJO).
We are currently in our second halving stage which results in a XJO reward of 4 instead of 8 or 16.

According to Joulecoin configuration, halving occurs every 2 years.

So, roughly 2 * (31 556 926 / 45) approx. 1 402 530 (this means that approximately block 1 402 530 should have the new block-award since 2 years have passed, but if the chain have had issues this could be longer or shorter)

If we look at Block explorer at around 1 400 000 (https://chainz.cryptoid.info/xjo/block.dws?000000000000f6256c21d60466bc9b7aab1704f5681e504546d1e9ca48074d9e.htm)
We can see that there still is the original 16 XJO reward.

So, let's calculate where 4 XJO happens. (4 * (31 556 926 / 45) approx. 2 805 060)

If we look at Block explorer again, but at 2 800 000 (https://chainz.cryptoid.info/xjo/block.dws?0000000000001561b85d4dde5aa9ada2fc491fbb1cee8fca9148df0f3e2d48b7.htm)
We can see that the 8 XJO reward is currently in place.

But if we check at block 2 805 060 (https://chainz.cryptoid.info/xjo/block.dws?0000000000000b807131df697a91d769f950b0aa04b4cd6cc09d7c50928d929b.htm)
We can confirm that the 4 XJO reward have indeed started occurring.

Disclaimer: I know this math is not preferred*

Introvard

newbie

Activity: 1

Merit: 0

>>Block reward: 16 XJO

When solo decoding a block, I get 4 xjo instead of 16 xjo. Why? Undecided

fukuroji

newbie

Activity: 14

Merit: 0

I think many people will participate in this business. New concept with innovative technology and good scalability of the blockchain with the 0 fees transactions.

shinohai

full member

Activity: 267

Merit: 109

Quote from: dalslandan200 on September 11, 2018, 12:32:03 AM

Quote from: IMZ Noo Account on September 09, 2018, 11:07:31 PM

We are getting better:

encrypt a message. Run it through a paste bin. Send the URL as a tx comment.

Made a web page where it is possible to encrypt a message via AES encryption with a key.

The compression ratio isn't perfect, but it increases to 67.4% before 240 character limit is reached.

However website linking is an awesome way to save storage for the Blockchain.

I got the following number for efficiency on the encryption compression ratio:

Code:

0.341 IN:15 OUT:44
0.484 IN:31 OUT:64
0.583 IN:63 OUT:108
0.617 IN:79 OUT:128
0.625 IN:95 OUT:152
0.645 IN:111 OUT:172
0.662 IN:143 OUT:216
0.674 IN:159 OUT:236

So at a small encryption it is around 35%, going all the way to ~67% at its best (maximum length encryption).
Which provides an maximum input of 159 characters before encryption, resulting in a 236 character long hash.

It's made possible with Javascript, so everything is happening local.
GitHub: https://github.com/brix/crypto-js/tree/release-3.1.2

I haven't made the first encrypted transaction message via the website yet.
Probably will later.

I had issues making clipboard button cross-browser compatibility with legacy support. So I have not missed this, I just wasn't happy with the current outcome.
Regarding the possibility to download the web page and run on other machines which are not connected to the internet, is also something I have in the pipeline.

Introducing: https://joulecoin.info/encrypt.html
- Online AES encryption and decryption made in mind for Joulecoin transaction comments.

Appears github is down this morning, but I will definitely check this out as soon as they come back up today and report back in.

EDIT Finally was able to check it out, very nice work. Please keep us apprised of this and will gladly test with IMZ.

dalslandan200

newbie

Activity: 30

Merit: 0

Quote from: shinohai on September 07, 2018, 08:51:42 AM

For now, I am simply blacklisting older versions that try to connect to my client.

Just as I suspected did new checkpoints resolve the issue with older 0.9.X.X trying to connect.

Made a GitHub gist here with checkpoints only: https://gist.github.com/dalslandan200/263e0ddbc2ddd32ff492ecb5ed84f710

dalslandan200

newbie

Activity: 30

Merit: 0

Quote from: IMZ Noo Account on September 09, 2018, 11:07:31 PM

We are getting better:

encrypt a message. Run it through a paste bin. Send the URL as a tx comment.

Made a web page where it is possible to encrypt a message via AES encryption with a key.

The compression ratio isn't perfect, but it increases to 67.4% before 240 character limit is reached.

However website linking is an awesome way to save storage for the Blockchain.

I got the following number for efficiency on the encryption compression ratio:

Code:

0.341 IN:15 OUT:44
0.484 IN:31 OUT:64
0.583 IN:63 OUT:108
0.617 IN:79 OUT:128
0.625 IN:95 OUT:152
0.645 IN:111 OUT:172
0.662 IN:143 OUT:216
0.674 IN:159 OUT:236

So at a small encryption it is around 35%, going all the way to ~67% at its best (maximum length encryption).
Which provides an maximum input of 159 characters before encryption, resulting in a 236 character long hash.

It's made possible with Javascript, so everything is happening local.
GitHub: https://github.com/brix/crypto-js/tree/release-3.1.2

I haven't made the first encrypted transaction message via the website yet.
Probably will later.

I had issues making clipboard button cross-browser compatibility with legacy support. So I have not missed this, I just wasn't happy with the current outcome.
Regarding the possibility to download the web page and run on other machines which are not connected to the internet, is also something I have in the pipeline.

Introducing: https://joulecoin.info/encrypt.html
- Online AES encryption and decryption made in mind for Joulecoin transaction comments.

shinohai

full member

Activity: 267

Merit: 109

Quote from: IMZ Noo Account on September 09, 2018, 11:07:31 PM

We are getting better:

encrypt a message. Run it through a paste bin. Send the URL as a tx comment.

As you know, I've been working on a telegram bot for a few weeks now - a W.I.P. is being able to do this directly from our chat. As it sits, can already check price, network nodes, explore blockchain, etc.

DLX - Membership has it's privileges. (tm) Cool

IMZ Noo Account

member

Activity: 746

Merit: 26

We are getting better:

encrypt a message. Run it through a paste bin. Send the URL as a tx comment.

shinohai

full member

Activity: 267

Merit: 109

Here is a list of nodes my telegram bot returns, appears there are still quite a few running old versions of the client:

Code:

[
{
"subver": "/Satoshi:0.10.4.1/",
"protocol": 70003,
"nodes": [
"165.227.226.221",
"217.169.182.114",
"78.129.185.31"
]
},
{
"subver": "/Satoshi:0.10.4.2/",
"protocol": 70003,
"nodes": [
"108.170.1.134",
"121.215.18.43",
"140.0.53.177",
"158.174.16.27",
"173.249.20.203",
"173.249.34.241",
"176.31.255.29",
"176.31.53.107",
"176.9.25.79",
"178.128.200.126",
"183.195.46.116",
"185.28.249.80",
"188.165.235.208",
"188.241.58.126",
"192.99.19.133",
"194.158.201.106",
"194.19.235.71",
"194.32.77.32",
"195.201.10.19",
"198.27.81.114",
"208.94.242.218",
"213.147.177.64",
"213.148.193.153",
"217.175.119.125",
"23.111.174.246",
"31.0.122.153",
"37.45.166.189",
"45.33.22.9",
"46.23.35.70",
"5.189.186.124",
"62.210.177.156",
"62.210.180.148",
"71.206.73.12",
"74.124.24.228",
"75.164.231.159",
"75.169.62.203",
"77.249.213.25",
"77.37.209.233",
"77.95.36.184",
"79.173.118.160",
"79.72.225.171",
"79.72.227.250",
"80.218.217.199",
"85.14.242.77",
"86.177.207.136",
"86.99.172.188",
"88.22.208.79",
"92.35.81.84",
"94.130.16.85",
"98.116.109.15"
]
},
{
"subver": "/Satoshi:0.10.4/",
"protocol": 70003,
"nodes": [
"161.53.18.50",
"173.212.202.33",
"198.50.204.112",
"50.225.198.67"
]
},
{
"subver": "/Satoshi:0.9.2.4/",
"protocol": 70002,
"nodes": [
"91.121.221.92"
]
},
{
"subver": "/Satoshi:0.9.2.5/",
"protocol": 70002,
"nodes": [
"52.14.92.197"
]
},
{
"subver": "/Satoshi:0.9.2.6/",
"protocol": 70002,
"nodes": [
"188.134.72.213",
"24.61.14.159",
"5.127.79.43",
"63.247.147.166",
"97.93.182.237"
]
},
{
"subver": "/Satoshi:0.9.2.7/",
"protocol": 70002,
"nodes": [
"213.21.201.153"
]
},
{
"subver": "/Satoshi:0.9.2.8/",
"protocol": 70002,
"nodes": [
"162.251.150.125"
]
}
]

For now, I am simply blacklisting older versions that try to connect to my client.

Topic: [ANN] [XJO] Joulecoin | SHA256 | First SHA256 data coin | Major upgrade 0.10.4.2 - page 11. (Read 139724 times)