2836
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2837
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 25, 2018, 02:08:25 PM »Theres been at least 3 masternodes running, Ive been one of them I updated to v1.1.5.5 three days ago, Updating now to latest version 1.1.5.5d
Togo- have you successfully tested the Contact list and Gospellink list, and is it good?
In the next version, the 1155d, you guys can please test the Diagnostic and Add buttons on the DC page- these do the same things as we test from the command line - except appear in the message box.
Im thinking for a brand new newbie, they will be able to install boinc, click Add Rosetta, then click Associate Rosetta.
Let me circle back around and re-test our blacklist and our team percentage and our non-biblepay PODC amount.
2838
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 23, 2018, 08:04:41 AM »
Jaap,
Thanks for testing. The reason rosettadiagnostics requires the e-mail pass in the arguments is we use it to check if an account exists with rosetta or not first, and that lets us make the decision on replying with the right narrative if a Rosetta account needs to be created or not.
I was thinking the way this could be implemented from the GUI is we put two more buttons on the DC page (Rosetta Diagnostics, and Set-Up Rosetta), and we use the same info populated on the page (the user and pass) to call the function, and we show the result in a messagebox.
Then in this next baby step, we can change the directions for new users to be something like : Install boinc, Click Set-Up Rosetta, Click Associate... etc.
On the nice UI pages etc, I was thinking we might be able to store more schema info in IPFS, and create a "Menu" object. It might be possible for me to add menu items that point to business objects. That would be an IPFS-driven menu system. Then the menu in the wallet is extended by what menu records exist; and we link for example "Gospel Link" to the Gospel Link List (from the Menu value for gospellink).
Havent though about letter writing yet, but I thought of what might be a good one: Our expenses and revenue being stored in IPFS. If we make an object for expense and one for revenue, we could port whats in the pool accountability over to the wallet. I think in order to do that, the permissions must be done first, otherwise hackers will deface the records (and that would of course is not an option for the accountability records). They have to be readable by all, but writable by the authorized signer.
Thanks for testing. The reason rosettadiagnostics requires the e-mail pass in the arguments is we use it to check if an account exists with rosetta or not first, and that lets us make the decision on replying with the right narrative if a Rosetta account needs to be created or not.
I was thinking the way this could be implemented from the GUI is we put two more buttons on the DC page (Rosetta Diagnostics, and Set-Up Rosetta), and we use the same info populated on the page (the user and pass) to call the function, and we show the result in a messagebox.
Then in this next baby step, we can change the directions for new users to be something like : Install boinc, Click Set-Up Rosetta, Click Associate... etc.
On the nice UI pages etc, I was thinking we might be able to store more schema info in IPFS, and create a "Menu" object. It might be possible for me to add menu items that point to business objects. That would be an IPFS-driven menu system. Then the menu in the wallet is extended by what menu records exist; and we link for example "Gospel Link" to the Gospel Link List (from the Menu value for gospellink).
Havent though about letter writing yet, but I thought of what might be a good one: Our expenses and revenue being stored in IPFS. If we make an object for expense and one for revenue, we could port whats in the pool accountability over to the wallet. I think in order to do that, the permissions must be done first, otherwise hackers will deface the records (and that would of course is not an option for the accountability records). They have to be readable by all, but writable by the authorized signer.
2839
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 22, 2018, 06:21:01 PM »For contacts, is specific long & lat a good idea? I'd worry someone who wants to target a group specifically could use it for evil. I wonder if long & lat should be close but not exact... like round up to zip code or census block group. So, you get a general idea of where someone is, but not exact location. The final disclosure can occur interpersonally.
I guess its up to the user to do what they want, and what features we use it for.
A public church can put the exact coordinates and maybe people who want to Tithe in BBP can go to that church.
The long & lat might be useful in the great tribulation if someone has a Christian camp that accepts other Christians, when things start getting bad.
2840
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 22, 2018, 02:38:26 PM »
Windows is deployed.
EDIT: Ok, the two boinc diagnostics commands should work in windows now (1155c has been deployed).
EDIT: Ok, the two boinc diagnostics commands should work in windows now (1155c has been deployed).
2841
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 22, 2018, 12:57:56 PM »
Hi All,
Here are some of the new test cases:
1. Diagnosing Rosetta: type 'exec rosettadiagnostics'. This command prints if Boinc is installed or not, if a rosetta account exists, and if Rosetta is attached and crunching. Note that this does not work on windows yet, but it will within a couple days (as a couple values need entered in the code for windows). Although this is not a GUI (yet) this was one thing we needed to provide the ability to make a GUI work.
2. Auto attaching RAH for a brand new user: type 'exec attachrosetta e-mail pass'. This command won't harm your setup if you are already working so have no fear in trying it. Its basically an end-end test that tries to fix anything it finds that is wrong. If boinc isn't installed, it tells you to install boinc and stops. If an account does not exist, it creates one. If RAH is not attached, it attaches RAH. This command also does not work on windows yet, but will within a couple days.
3. Business objects. Now we have the capability to create multiple types of business objects in IPFS. We currently have 3: object, contact and gospellink. Note that the contents of each business object record are stored in IPFS not the chain. To see the list of gospellink's for example, type exec bolist gospellink.
4. Navigating to a List (of business object records). To keep our BO system generic, instead of promoting hundreds of UI pages at this stage, the navigation is done through programmatic jumps from object to object (not from UI bound to objects). So let's test the display of the list of gospellinks: From the menu, click Business Object List. This shows the master list of business objects (we have 3). Right click on Gospel Link, then click List. The system will then show a list of Gospel Links.
5. Navigating to a URL in a business object: Right now we have Testimony URL in Contact and Video URL in GospelLink. To view a video for example, right click on the GospelLink and click NavigateTo. You can also do this from Contact. The system searches for a field called "URL" and navigates to that field value (currently).
6. Add your own gospellink: Type 'exec addgospellink url notes' (Note that any value with a space in it must be surrounded by quotes). In the future we will have an Add page to add a business object record to any business object.
Hopefully you can see the value in business objects, as a generic store that Biblepay may possibly charge to lease individual organization specific permissioned objects. Realize in the future we will need to add permissions to keep an org's objects from being defaced by the public.
Here are some of the new test cases:
1. Diagnosing Rosetta: type 'exec rosettadiagnostics'. This command prints if Boinc is installed or not, if a rosetta account exists, and if Rosetta is attached and crunching. Note that this does not work on windows yet, but it will within a couple days (as a couple values need entered in the code for windows). Although this is not a GUI (yet) this was one thing we needed to provide the ability to make a GUI work.
2. Auto attaching RAH for a brand new user: type 'exec attachrosetta e-mail pass'. This command won't harm your setup if you are already working so have no fear in trying it. Its basically an end-end test that tries to fix anything it finds that is wrong. If boinc isn't installed, it tells you to install boinc and stops. If an account does not exist, it creates one. If RAH is not attached, it attaches RAH. This command also does not work on windows yet, but will within a couple days.
3. Business objects. Now we have the capability to create multiple types of business objects in IPFS. We currently have 3: object, contact and gospellink. Note that the contents of each business object record are stored in IPFS not the chain. To see the list of gospellink's for example, type exec bolist gospellink.
4. Navigating to a List (of business object records). To keep our BO system generic, instead of promoting hundreds of UI pages at this stage, the navigation is done through programmatic jumps from object to object (not from UI bound to objects). So let's test the display of the list of gospellinks: From the menu, click Business Object List. This shows the master list of business objects (we have 3). Right click on Gospel Link, then click List. The system will then show a list of Gospel Links.
5. Navigating to a URL in a business object: Right now we have Testimony URL in Contact and Video URL in GospelLink. To view a video for example, right click on the GospelLink and click NavigateTo. You can also do this from Contact. The system searches for a field called "URL" and navigates to that field value (currently).
6. Add your own gospellink: Type 'exec addgospellink url notes' (Note that any value with a space in it must be surrounded by quotes). In the future we will have an Add page to add a business object record to any business object.
Hopefully you can see the value in business objects, as a generic store that Biblepay may possibly charge to lease individual organization specific permissioned objects. Realize in the future we will need to add permissions to keep an org's objects from being defaced by the public.
2842
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 22, 2018, 11:24:37 AM »
Update: 1.1.5.5 has been checked in for TestNet, please upgrade.
Windows is compiling.
I will Blog ASAP on what was added and how we can test it.
Windows is compiling.
I will Blog ASAP on what was added and how we can test it.
2843
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 20, 2018, 05:15:46 PM »
So I added some more handling to the area of "ancestor not found". I found a bug in Contact Add - fixed - will be in the next testnet version.
Im working on automating BOINC setup for brand new cancer miners.
Let's pause for a little bit until the next version is ready, then we can test all this together.
Im working on automating BOINC setup for brand new cancer miners.
Let's pause for a little bit until the next version is ready, then we can test all this together.
2844
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 20, 2018, 10:43:07 AM »
Oh one more thing I just remembered, if anyone does receive that 'block has no ancestor' and crash, you can also make a copy of your testnet chainstate and blocks folders, and zip it and send to me, or simply keep it in order to have it to reproduce the error again in valgrind.
2845
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 20, 2018, 09:41:58 AM »Sorry, I already -reindexed itSure, it should be easy as the defaults usually work. Once you have valgrind installed, depending on how you launch biblepay (IE either "./biblepay-qt" or "./biblepayd") replace that string with this:
But I've installed valgrind in case it ever happens again. Can't seem to get it working in all my noobness though... Could you tell me what specific command I should use?
cd ~/biblepay
valgrind ./biblepay-qt
For example would start the QT wallet with valgrind running. You can put all your normal parameters after the ./biblepay-qt also. It might be easier to pipe the output to a log file since the log would be long (like >vallog.txt) etc. If you dont pipe to a log you can scroll back through the end of the trace and see functions and line numbers. We usually need the last stack trace (the whole section to see how it was called). Since some functions call other functions etc.
2846
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 19, 2018, 05:18:14 PM »After restarting the 85.29 node I got the same 'Segmentation fault' error that Togo got:Code: [Select]ERROR: Found block with no ancestor
2018-09-19 21:17:36 ERROR: Block has no ancestor.
2018-09-19 21:17:36 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-09-19 21:17:36 Misbehaving: 47.189.72.5:58842 (0 -> 3)
2018-09-19 21:17:36 ProcessNewBlock : ACCEPTED
Thats kind of cool; if you still have that node in that state, could you sudo apt-get install valgrind, valgrind ./biblepay and see what line it breaks on?
If not we'll eventually figure it out, but you will probably have to reindex to get past it.
I seem to be back to normal on all nodes now.
I'll do my best to find that bug. I know we fixed the major fork issue in this version, now we need a couple more minor things... checking.
2847
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 19, 2018, 02:59:04 PM »Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexedCode: [Select]Segmentation fault (core dumped)
tail debug.logCode: [Select]ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767
Im going to clean and reindex again
84.29 is running 1154. I know that area of code, we crashed a couple times there in the past - there is even some code in there to try to prevent the crash. Its really elusive because every time I hear this and try to valgrind it, there is no way to reproduce the exact situation again - I know it has something to do with having a lot of forks in your getchaintips. I think one of the forks best block hashes is NULL to the wallet. But we dont save NULL blocks in the map. I did check Dash to see if they changed that but not yet.
2848
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 19, 2018, 02:30:58 PM »I have three wallets. Only one was syncing to the tip (and had the same blockhash as you have), but that one didn't have a CPID associated with it. I just associated a CPID with that one, so let's wait and see if that's going to work.
The other two I'll try to resync...
Something is starting to happen now... I think.
Yes- all the wallets are clicking up now in tandem. We had some type of problem based on where we sputtered out (right at the block before the last boinc superblock) and since our masternodes were all dead, the wallet couldnt come to consensus on that superblock. Now we are past it and we have 6 or so testers online. We just need to bring up our sancs now.
2849
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 19, 2018, 11:56:57 AM »Alright, I've updated all my wallets and deleted the .dat's you suggested. Resynching now...
Thanks all - Ive relaunched 4 nodes and 2 are mining. Although each block I solve is having trouble being added to the other nodes.
But, I believe we are back in the same state we were in prior to the QT fiasco, so Im thinking we just need another miner online now.
Lets be patient and see if another miner allows us to sync. Im on block :
getblockhash 67726
35fa0d84e64d0fb0b4ec6a05588d8b38b42967e5acbebaa5384e780d10f55728
2850
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: September 19, 2018, 07:38:37 AM »Oops, after I removed QT, I just realized one of the chain parameters in testnet was adjusted to look back 30 days for the QT 'governanceinfo' prior total (this was for future qt).... Sorry...
Please all, upgrade to 1.1.5.4b....
Building windows now.
We can talk about the cpids solving ability tomorrow after we resync again.
Thanks.
When you guys re-sync today, please delete your mnc*.* and mnp*.* files and the banlist.dat also first.
I have found that we may be caching a superblock (in the govobj system) with a bad payment - and I believe that will fix our sync issue in testnet.