$XAI Sapience AIFX - Decentralized AI | 11% PoS | PlumeDB,IBTP on Testnet

[UNO_owner]

I must admit, I'm a patient guy and bought XAI/XQN as an investment, but the weeks without the occasional update or communication do get annoying.  I certainly don't think it is unreasonable for Cedric to take 5 mins a week and post a paragraph of how things are progressing.  Hell, he's an old guy - he could have had a heart attack or something.

[Cornett]

I must admit, I'm a patient guy and bought XAI/XQN as an investment, but the weeks without the occasional update or communication do get annoying.  I certainly don't think it is unreasonable for Cedric to take 5 mins a week and post a paragraph of how things are progressing.  Hell, he's an old guy - he could have had a heart attack or something.

as we can see from the videos, he has a good health. I bet he will reveal something soon

[CedricQuotient]

There's a lot of great tech coming for this coin, the AI Core is just the beginning really... it is a lot of work but will be worth it in the end.  I'm working to get a series of things out the door, life stuff comes up and hence some delays, but that doesn't change what's coming.  I'm also trying to position things so that I can continue working full time on this past April for the foreseeable future, which would be ideal so we can keep cranking stuff out.
...
So we have AI Core coming that I've been talking about, and then we have a strategy to open up and capture a new market that I think only I/we have the actual capability to achieve in rapid fashion.  The AI Core stuff is hard/complicated, all the other stuff is relatively easy for me to bang out.  So we'll get through the AI core traffic jam and then step on the accelerator again.  TBH the hold up on the AI Core drop has not been tech or coding related, but just life related, shit happens that ties up my time, and then we continue on.
....

Thank you for your patience

edit:  And this stuff is coming soon.... It's not going to be like NautilusCoin with the POS fork that was coming for months and months and months and months  To put this into perspective, I built this entire platform in less than 3 months.  Compared to any enterprise project of similar scale and scope, that is an insane pace.  But in the crypto world, of course, we know that the space-time continuum is....compressed

I'm quite disappointed in this dev actually. It all looked promising a couple of months back, but the dev is not living up to the expectations he set himself. I understand that he might have bitten off more than he could chew (happens to the best of us), but at least don't leave us hanging out there, spend 5 minutes per week on a quick update or something. I'd say you owe that to the people who invested in your idea. I'll be patient for a bit longer, but as soon as something better comes a long i am out of here...

:shrug: If you want to sell then sell, there have been plenty of opportunities to exit.  The crypto landscape and alts in particular have dried up in terms of volume and viable revenue-generating activities.  XAI is a long term project, but I do have to earn a living too   I had been looking at a variety of avenues to bring some real funding into this project, but with the last stall-out in crypto trading activity most of those went dead or folks just left/stopped looking at crypto altogether.

We got some graphics proofs back from the designer that look fantastic, but it will be some time before he is complete with production ready designs.

I'll probably open source this project this weekend and just get the code out there for people to play with and see what the community comes up with.

[UNO_owner]

Yea, seriously.  WTF is that supposed to mean Cedric?  If I read between the lines, I read "I'm done - take the source code and do it yourself".

On March 26th you wrote "this stuff is coming soon".  2 months later with barely any updates and now as near as I can tell you appear to be totally backing out this project.

[Cornett]

Joe will open source XAI and will continue to work on this project. It's really good  

[CedricQuotient]

Joe will open source his work and will continue to work on this project. It's good 

Exactly.  The point of open sourcing it is so folks can compile it for various platforms, linux raspberry pi etc. and play around with it.  It's too much of a pain trying to maintain a public vs. closed version and two codebases.  I'm working on solving another linker issue then I'll push the code.

[thefix]

Joe will open source XAI and will continue to work on this project. It's really good  

I agree, never a smart move to keep all the burden on one person.

Most decent projects have more than one person working on the project.

[trader19]

Joe will open source XAI and will continue to work on this project. It's really good  

I agree, never a smart move to keep all the burden on one person.

Most decent projects have more than one person working on the project.

okay sounds interesting. watching

[CedricQuotient]

I pushed an update to github and tagged the last public version and the latest commit (6.1.14 and 6.2.21).  I'm still beating my head against the wall trying to get the Windows build to work, I had a workaround that I thought would work but it just results in strange undefined reference issues - which was to embed libqtlua within the source tree and build it that way.  But libqtlua is using headers with inline declarations and my suspicion is that mingw can't handle the mixing and matching like that.  I thought I had it working but when I did a make clean and tried to build from scratch it started spewing those issues again.  To build it on Linux you need Lua 5.3 and libqtlua 2.0, on my system I put them in ~/deps/lua and ~/deps/libqtlua, if you put them somewhere else you'll want to update the paths in the .pro file.  Works like a charm on Linux.

So what you'll see is that for IBTP the simple way I am doing the integration across coin networks is by filtering on the pchMessageStart.  I pre-load a directory of known chains:

Code:

struct SChain
{
public:
    std::string sChainName;
    std::string sCurrencyCode;
    unsigned char pchMessageOne;
    unsigned char pchMessageTwo;
    unsigned char pchMessageThree;
    unsigned char pchMessageFour;

    SChain()
    {
    }

    SChain(std::string sName, std::string sCode, unsigned char cOne, unsigned char cTwo, unsigned char cThree, unsigned char cFour)
    {
        sChainName = sName;
        sCurrencyCode = sCode;
        pchMessageOne = cOne;
        pchMessageTwo = cTwo;
        pchMessageThree = cThree;
        pchMessageFour = cFour;
    }
};

And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:

Code:

// Relay alerts
if(!pfrom->fForeignNode)
{

When the node first connects and does the version handshake, it detects if it is not an XAI note and in the IBTP directory and sets the fForeignNode flag.  And thats it, from then on you can differentiate between native or non-native blockchains and handle the messaging appropriately.

[Cornett]

I pushed an update to github and tagged the last public version and the latest commit (6.1.14 and 6.2.21).  I'm still beating my head against the wall trying to get the Windows build to work, I had a workaround that I thought would work but it just results in strange undefined reference issues - which was to embed libqtlua within the source tree and build it that way.  But libqtlua is using headers with inline declarations and my suspicion is that mingw can't handle the mixing and matching like that.  I thought I had it working but when I did a make clean and tried to build from scratch it started spewing those issues again.  To build it on Linux you need Lua 5.3 and libqtlua 2.0, on my system I put them in ~/deps/lua and ~/deps/libqtlua, if you put them somewhere else you'll want to update the paths in the .pro file.  Works like a charm on Linux.

So what you'll see is that for IBTP the simple way I am doing the integration across coin networks is by filtering on the pchMessageStart.  I pre-load a directory of known chains:

Code:

struct SChain
{
public:
    std::string sChainName;
    std::string sCurrencyCode;
    unsigned char pchMessageOne;
    unsigned char pchMessageTwo;
    unsigned char pchMessageThree;
    unsigned char pchMessageFour;

    SChain()
    {
    }

    SChain(std::string sName, std::string sCode, unsigned char cOne, unsigned char cTwo, unsigned char cThree, unsigned char cFour)
    {
        sChainName = sName;
        sCurrencyCode = sCode;
        pchMessageOne = cOne;
        pchMessageTwo = cTwo;
        pchMessageThree = cThree;
        pchMessageFour = cFour;
    }
};

And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:

Code:

// Relay alerts
if(!pfrom->fForeignNode)
{

When the node first connects and does the version handshake, it detects if it is not an XAI note and in the IBTP directory and sets the fForeignNode flag.  And thats it, from then on you can differentiate between native or non-native blockchains and handle the messaging appropriately.

I think that you and your professionalism will win this issues. What are your future plans, maybe you have some dates for the future events?

With regards, Cornett

[ethought]

Very cool Joe!! 

I have been playing with the new client and daemon and it is clear a lot of work has gone in to this so far.

[mightgetlucky]

Very cool Joe!! 

I have been playing with the new client and daemon and it is clear a lot of work has gone in to this so far.

One of the rare legit projects IMO.

[albert_mt]

i hoped this project would work out differently than most crypto do, but it seems this is the same and no real progress here. still this is a very cool project.

[runpaint]

I pushed an update to github and tagged the last public version and the latest commit (6.1.14 and 6.2.21).  I'm still beating my head against the wall trying to get the Windows build to work, I had a workaround that I thought would work but it just results in strange undefined reference issues - which was to embed libqtlua within the source tree and build it that way.  But libqtlua is using headers with inline declarations and my suspicion is that mingw can't handle the mixing and matching like that.  I thought I had it working but when I did a make clean and tried to build from scratch it started spewing those issues again.  To build it on Linux you need Lua 5.3 and libqtlua 2.0, on my system I put them in ~/deps/lua and ~/deps/libqtlua, if you put them somewhere else you'll want to update the paths in the .pro file.  Works like a charm on Linux.

So what you'll see is that for IBTP the simple way I am doing the integration across coin networks is by filtering on the pchMessageStart.  I pre-load a directory of known chains:

Code:

struct SChain
{
public:
    std::string sChainName;
    std::string sCurrencyCode;
    unsigned char pchMessageOne;
    unsigned char pchMessageTwo;
    unsigned char pchMessageThree;
    unsigned char pchMessageFour;

    SChain()
    {
    }

    SChain(std::string sName, std::string sCode, unsigned char cOne, unsigned char cTwo, unsigned char cThree, unsigned char cFour)
    {
        sChainName = sName;
        sCurrencyCode = sCode;
        pchMessageOne = cOne;
        pchMessageTwo = cTwo;
        pchMessageThree = cThree;
        pchMessageFour = cFour;
    }
};

And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:

Code:

// Relay alerts
if(!pfrom->fForeignNode)
{

When the node first connects and does the version handshake, it detects if it is not an XAI note and in the IBTP directory and sets the fForeignNode flag.  And thats it, from then on you can differentiate between native or non-native blockchains and handle the messaging appropriately.

Thank you, and keep up the good work!

[ethought]

i hoped this project would work out differently than most crypto do, but it seems this is the same and no real progress here. still this is a very cool project.

Did you look at the latest commits on Github??

[Cornett]

i hoped this project would work out differently than most crypto do, but it seems this is the same and no real progress here. still this is a very cool project.

Are you looked at Joe's Linkedin profile?

https://www.linkedin.com/in/joemozelesky



XAI Dev is one of the most professional persons in crypto world. He is chairman and CEO in Limitless Acuity LLC this days and collaborated with Microsoft in the past, are you realize this? He's got a 20+ years of experience in IT. He works with crypto technologies this days constantly. There are a lot of things behind the scene. These facts are enough for me to investing a lot in his work.

[albert_mt]

i hoped this project would work out differently than most crypto do, but it seems this is the same and no real progress here. still this is a very cool project.

Are you looked at Joe's Linkedin profile?

https://www.linkedin.com/in/joemozelesky



XAI Dev is one of the most professional persons in crypto world. He is chairman and CEO in Limitless Acuity LLC this days and collaborated with Microsoft in the past, are you realize this? He's got a 20+ years of experience in IT. He works with crypto technologies this days constantly. There are a lot of things behind the scene. These facts are enough for me to investing a lot in his work.

i said this is a very cool project. whether a one man business Limitless Acuity LLC can pull this off is remain to be seen. i understand you are very impressed by Joe's CV, probably quite rightly so, but there are many-many software developers with 20+ years of experience and only a very few of them can pull off what you are hoping from this project. still this is a cool project 

[ethought]

i hoped this project would work out differently than most crypto do, but it seems this is the same and no real progress here. still this is a very cool project.

Are you looked at Joe's Linkedin profile?

https://www.linkedin.com/in/joemozelesky



XAI Dev is one of the most professional persons in crypto world. He is chairman and CEO in Limitless Acuity LLC this days and collaborated with Microsoft in the past, are you realize this? He's got a 20+ years of experience in IT. He works with crypto technologies this days constantly. There are a lot of things behind the scene. These facts are enough for me to investing a lot in his work.

i said this is a very cool project. whether a one man business Limitless Acuity LLC can pull this off is remain to be seen. i understand you are very impressed by Joe's CV, probably quite rightly so, but there are many-many software developers with 20+ years of experience and only a very few of them can pull off what you are hoping from this project. still this is a cool project 

One of the reasons Joe decided to open source the project is so that it is not a one man project - others can now contribute.

[MadCow]

Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks

[hexdump]

Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks

same here