Topic: $XAI Sapience AIFX - Decentralized AI | 11% PoS | PlumeDB,IBTP on Testnet - page 13. (Read 150224 times)
May 31, 2015, 10:55:34 AM
Price is a reflection of diminished positive sentiment towards the coin and roadmap i.e. it's pattern of previously unfulfilled announcements.
May 31, 2015, 10:18:27 AM
Only six, I usually don't mint this coin much so I don't have many nodes. (I can't afford to purchase yet, I'm waiting for some dumps)
Perfect timing, a dump has taken place (somebody holding 15k XAI)
- Maybe people do not understand the project and the timeline.
- Low volume + low 'support'.
- Dumping $XAI to jump on a coin which has already been hyped up
There's too many possible reasons, maybe a wallet update or something may keep those short term investors happy, however I am long term.
May 31, 2015, 10:07:37 AM
Only six, I usually don't mint this coin much so I don't have many nodes. (I can't afford to purchase yet, I'm waiting for some dumps)
Perfect timing, a dump has taken place (somebody holding 15k XAI)
May 31, 2015, 08:29:39 AM
Only six, I usually don't mint this coin much so I don't have many nodes. (I can't afford to purchase yet, I'm waiting for some dumps)
Perfect timing, a dump has taken place (somebody holding 15k XAI)
May 31, 2015, 08:08:38 AM
Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks
thanks
http://www.blocktree.io/peers/XAI/
May 31, 2015, 12:07:50 AM
Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks
thanks
same here
Only six, I usually don't mint this coin much so I don't have many nodes. (I can't afford to purchase yet, I'm waiting for some dumps)
Code:
[
{
"addr" : "62.43.140.213:30894",
"services" : "00000001",
"lastsend" : 1433044999,
"lastrecv" : 1433045003,
"conntime" : 1433021922,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251318,
"banscore" : 0
},
{
"addr" : "144.76.239.66:30894",
"services" : "00000001",
"lastsend" : 1433044999,
"lastrecv" : 1433045001,
"conntime" : 1433021965,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251320,
"banscore" : 0
},
{
"addr" : "98.175.59.71:30894",
"services" : "00000001",
"lastsend" : 1433045013,
"lastrecv" : 1433045014,
"conntime" : 1433022219,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251324,
"banscore" : 0
},
{
"addr" : "88.196.244.208:30894",
"services" : "00000001",
"lastsend" : 1433045013,
"lastrecv" : 1433045014,
"conntime" : 1433022238,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251324,
"banscore" : 0
},
{
"addr" : "101.165.90.37:30894",
"services" : "00000001",
"lastsend" : 1433044999,
"lastrecv" : 1433045000,
"conntime" : 1433022332,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251325,
"banscore" : 0
},
{
"addr" : "108.35.126.79:30894",
"services" : "00000001",
"lastsend" : 1433044945,
"lastrecv" : 1433044999,
"conntime" : 1433022333,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251325,
"banscore" : 0
}
]
{
"addr" : "62.43.140.213:30894",
"services" : "00000001",
"lastsend" : 1433044999,
"lastrecv" : 1433045003,
"conntime" : 1433021922,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251318,
"banscore" : 0
},
{
"addr" : "144.76.239.66:30894",
"services" : "00000001",
"lastsend" : 1433044999,
"lastrecv" : 1433045001,
"conntime" : 1433021965,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251320,
"banscore" : 0
},
{
"addr" : "98.175.59.71:30894",
"services" : "00000001",
"lastsend" : 1433045013,
"lastrecv" : 1433045014,
"conntime" : 1433022219,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251324,
"banscore" : 0
},
{
"addr" : "88.196.244.208:30894",
"services" : "00000001",
"lastsend" : 1433045013,
"lastrecv" : 1433045014,
"conntime" : 1433022238,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251324,
"banscore" : 0
},
{
"addr" : "101.165.90.37:30894",
"services" : "00000001",
"lastsend" : 1433044999,
"lastrecv" : 1433045000,
"conntime" : 1433022332,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251325,
"banscore" : 0
},
{
"addr" : "108.35.126.79:30894",
"services" : "00000001",
"lastsend" : 1433044945,
"lastrecv" : 1433044999,
"conntime" : 1433022333,
"version" : 60013,
"subver" : "/ProfitReaper:1.6.1.14/",
"inbound" : false,
"startingheight" : 251325,
"banscore" : 0
}
]
May 30, 2015, 04:37:12 PM
I am about to pick up a few more, been away for a while glad to see we are still in business
May 30, 2015, 03:37:57 PM
Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks
thanks
same here
May 30, 2015, 03:17:08 AM
Could someone post a few nodes, I can't sync anymore (going through TOR)
thanks
thanks
May 29, 2015, 10:59:52 AM
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.
May 29, 2015, 09:50:01 AM
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
May 29, 2015, 08:57:20 AM
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.
May 29, 2015, 08:16:28 AM
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??
May 29, 2015, 08:09:42 AM
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:
And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:
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.
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;
}
};
{
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)
{
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!
May 29, 2015, 06:54:12 AM
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.
May 28, 2015, 01:39:33 PM
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.
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.
May 28, 2015, 01:36:50 PM
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.
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.
May 26, 2015, 05:50:16 AM
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:
And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:
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.
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;
}
};
{
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)
{
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
May 26, 2015, 12:16:01 AM
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:
And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:
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.
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;
}
};
{
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)
{
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.
May 25, 2015, 04:06:08 PM
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.
Jump to: