BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

a found another problem with pog
i'm trying to cleanup wallet, there is over 1000 chunks with ~1 bbp, if i select all of them and try to move it together, it throws: transaction too large (> 150kB)
so how can i cleanup wallet without clicking hundreds of chunks manualy?, also select all is not suitable as i have there tithe piles
there is definitely missing a tool to do this automaticaly
it was small wallet with only 1m bbp so not tithing frequently, what if i'll use large wallet with >10m bbp? there will be 10k chunks after while, impossible to cleanup manualy

Yeah, this is addressed in the next design.

For now you can do some small exec bankroll commands to combine those back into bigger bills.  Each exec bankroll just has to be small enough to keep each transaction below 100K in size.

Since POG is off now, the problem won't re-emerge.

(In the next design, everything we do is once per day.)

[sunk818]

a found another problem with pog
i'm trying to cleanup wallet, there is over 1000 chunks with ~1 bbp, if i select all of them and try to move it together, it throws: transaction too large (> 150kB)
so how can i cleanup wallet without clicking hundreds of chunks manualy?, also select all is not suitable as i have there tithe piles
there is definitely missing a tool to do this automaticaly
it was small wallet with only 1m bbp so not tithing frequently, what if i'll use large wallet with >10m bbp? there will be 10k chunks after while, impossible to cleanup manualy

Rob previously said an exec consolidate was not necessary.

I've had to consolidate the dust manually.

There's a GitHub issue for it already but looks like Rob is going to change pog based on what he learned with pog v1 and pog v2. Pog monkey 🐵 approves!!!

[bible_pay]

a found another problem with pog
i'm trying to cleanup wallet, there is over 1000 chunks with ~1 bbp, if i select all of them and try to move it together, it throws: transaction too large (> 150kB)
so how can i cleanup wallet without clicking hundreds of chunks manualy?, also select all is not suitable as i have there tithe piles
there is definitely missing a tool to do this automaticaly
it was small wallet with only 1m bbp so not tithing frequently, what if i'll use large wallet with >10m bbp? there will be 10k chunks after while, impossible to cleanup manualy

Rob previously said an exec consolidate was not necessary.

I've had to consolidate the dust manually.

There's a GitHub issue for it already but looks like Rob is going to change pog based on what he learned with pog v1 and pog v2. Pog monkey 🐵 approves!!!

Well I'm not contradicting myself though, the thing is if we had a successful POG lifecycle (IE, a full budget allocated to POG), we still might have enjoyed more widespread adoption over a year, and, naturally, I would have tweaked 'exec bankroll' to automatically consolidate dust (and more users would have theoretically resulted in less tithes per day per user).

But, I like more efficient machines, and being aware of what we learned in POGv1, we might as well design the entire system to be as scalable and efficient as possible with no network spam.  Looking at these new GSC requirements it appears we can do that without losing anything! 

To a bright future....

[sunk818]

a found another problem with pog
i'm trying to cleanup wallet, there is over 1000 chunks with ~1 bbp, if i select all of them and try to move it together, it throws: transaction too large (> 150kB)
so how can i cleanup wallet without clicking hundreds of chunks manualy?, also select all is not suitable as i have there tithe piles
there is definitely missing a tool to do this automaticaly
it was small wallet with only 1m bbp so not tithing frequently, what if i'll use large wallet with >10m bbp? there will be 10k chunks after while, impossible to cleanup manualy

Rob previously said an exec consolidate was not necessary.

I've had to consolidate the dust manually.

There's a GitHub issue for it already but looks like Rob is going to change pog based on what he learned with pog v1 and pog v2. Pog monkey 🐵 approves!!!

Well I'm not contradicting myself though, the thing is if we had a successful POG lifecycle (IE, a full budget allocated to POG), we still might have enjoyed more widespread adoption over a year, and, naturally, I would have tweaked 'exec bankroll' to automatically consolidate dust (and more users would have theoretically resulted in less tithes per day per user).

But, I like more efficient machines, and being aware of what we learned in POGv1, we might as well design the entire system to be as scalable and efficient as possible with no network spam.  Looking at these new GSC requirements it appears we can do that without losing anything! 

You mentioned daily tithing. What are your thoughts for less network spam of tithing?

[bible_pay]

a found another problem with pog
i'm trying to cleanup wallet, there is over 1000 chunks with ~1 bbp, if i select all of them and try to move it together, it throws: transaction too large (> 150kB)
so how can i cleanup wallet without clicking hundreds of chunks manualy?, also select all is not suitable as i have there tithe piles
there is definitely missing a tool to do this automaticaly
it was small wallet with only 1m bbp so not tithing frequently, what if i'll use large wallet with >10m bbp? there will be 10k chunks after while, impossible to cleanup manualy

Rob previously said an exec consolidate was not necessary.

I've had to consolidate the dust manually.

There's a GitHub issue for it already but looks like Rob is going to change pog based on what he learned with pog v1 and pog v2. Pog monkey 🐵 approves!!!

Well I'm not contradicting myself though, the thing is if we had a successful POG lifecycle (IE, a full budget allocated to POG), we still might have enjoyed more widespread adoption over a year, and, naturally, I would have tweaked 'exec bankroll' to automatically consolidate dust (and more users would have theoretically resulted in less tithes per day per user).

But, I like more efficient machines, and being aware of what we learned in POGv1, we might as well design the entire system to be as scalable and efficient as possible with no network spam.  Looking at these new GSC requirements it appears we can do that without losing anything! 

You mentioned daily tithing. What are your thoughts for less network spam of tithing?

All information will be released in the first GSC document by Monday.

[sunk818]

“Do all things without grumbling or disputing, that you may be blameless and innocent, children of God without blemish in the midst of a crooked and twisted generation, among whom you shine as lights in the world,”
Philippians‬ 2:14-15‬ ESV‬‬

[togoshigekata]

Masternodes.Online is still not synced for us
https://masternodes.online/currencies/BBP/

From their twitter post they may delist us this Friday
https://twitter.com/_mn_o_/status/1105958103512571904

I just sent them an email to check back up on them,
6 days ago I sent them update instructions

Here is the email chain:

using the latest version we are unable to keep the daemon running stable.

Syncing from scratch works fine and we are able to get to head according to the debug log:

2019-03-17 12:02:18 UpdateTip: new best=6c92f07b49206cbea33eb4bd39c85186413035f58461a11cfa396dbce2475408  height=107556  log2_work=59.19035  tx=910638  date=2019-03-17 12:01:52 progress=0.999999  cache=9.6MiB(25487tx)
2019-03-17 12:02:18 ProcessNewBlock : ACCEPTED

However, we are unable to run any RPC commands at this point, see the output from any of the commands we run.

biblepay-cli getinfo
error: couldn't parse reply from server

biblepay-cli getblockcount
error: couldn't parse reply from server

This has been replicated every time we run the daemon.

Upon restarting, we can still run getinfo as shown below:

 biblepay-cli getinfo
{
  "version": 1020001,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.2.0.1",
  "subversion": "/Biblepay Core:1.2.0.1/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 0,
  "proxy": "",
  "difficulty": 4.656542373906925e-09,
  "testnet": false,
  "keypoololdest": 1552807115,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Do you have any solution?

Looks like your on latest version hmmm

Id probably recommend doing an update/install again, just to be sure,
then a full clean (deletion) of the /blocks and /chainstate folders and the .dat files
and then do a reindex again:
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

I assume you guys are on Linux?

cd biblepay/src
./biblepay-cli stop
git pull origin master
sudo make

cd ~/.biblepaycore
rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat

cd biblepay/src
./biblepayd -daemon -reindex

Let me know if this works for you guys

Just checking back, Were you guys able to get BiblePay working?

We run the daemon from scratch and have done it on multiple servers so the issue is not some stale block info.

All the daemons on MNO are our own builds - not the pre-compiled binaries. Can you confirm that the code in github is the latest version and is what you use to build the binaries? We are on LInux (Ubuntu 16.04)

Please note that we compile and deploy each and every commit. Biblepay is one of the most active coins in that regard - we have had 184 builds since adding it to MNO and all of them were deployed without issue.

This latest version is different though. As none of the other builds have had any kind of issue and we haven't changed our build settings could you please double check that the code is right?

[bible_pay]

Masternodes.Online is still not synced for us
https://masternodes.online/currencies/BBP/

From their twitter post they may delist us this Friday
https://twitter.com/_mn_o_/status/1105958103512571904

I just sent them an email to check back up on them,
6 days ago I sent them update instructions

Here is the email chain:

using the latest version we are unable to keep the daemon running stable.

Syncing from scratch works fine and we are able to get to head according to the debug log:

2019-03-17 12:02:18 UpdateTip: new best=6c92f07b49206cbea33eb4bd39c85186413035f58461a11cfa396dbce2475408  height=107556  log2_work=59.19035  tx=910638  date=2019-03-17 12:01:52 progress=0.999999  cache=9.6MiB(25487tx)
2019-03-17 12:02:18 ProcessNewBlock : ACCEPTED

However, we are unable to run any RPC commands at this point, see the output from any of the commands we run.

biblepay-cli getinfo
error: couldn't parse reply from server

biblepay-cli getblockcount
error: couldn't parse reply from server

This has been replicated every time we run the daemon.

Upon restarting, we can still run getinfo as shown below:

 biblepay-cli getinfo
{
  "version": 1020001,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.2.0.1",
  "subversion": "/Biblepay Core:1.2.0.1/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 0,
  "proxy": "",
  "difficulty": 4.656542373906925e-09,
  "testnet": false,
  "keypoololdest": 1552807115,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Do you have any solution?

Looks like your on latest version hmmm

Id probably recommend doing an update/install again, just to be sure,
then a full clean (deletion) of the /blocks and /chainstate folders and the .dat files
and then do a reindex again:
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

I assume you guys are on Linux?

cd biblepay/src
./biblepay-cli stop
git pull origin master
sudo make

cd ~/.biblepaycore
rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat

cd biblepay/src
./biblepayd -daemon -reindex

Let me know if this works for you guys

Just checking back, Were you guys able to get BiblePay working?

We run the daemon from scratch and have done it on multiple servers so the issue is not some stale block info.

All the daemons on MNO are our own builds - not the pre-compiled binaries. Can you confirm that the code in github is the latest version and is what you use to build the binaries? We are on LInux (Ubuntu 16.04)

Please note that we compile and deploy each and every commit. Biblepay is one of the most active coins in that regard - we have had 184 builds since adding it to MNO and all of them were deployed without issue.

This latest version is different though. As none of the other builds have had any kind of issue and we haven't changed our build settings could you please double check that the code is right?

I recommend honing in this specific problem:
biblepay-cli getinfo
error: couldn't parse reply from server

biblepay-cli getblockcount
error: couldn't parse reply from server


Could you tell them that Rob (and You) ran these two commands from biblepay-cli (from the compiled version in linux) these commands do not error out.

See if you can reproduce either one, using biblepay-cli then tell them Rob believes there is no error - please provide us more details to reproduce.

Feel free to send them my e-mail and Ill be glad to reply to them also.

EDIT: Regarding that they made "184 builds" for us please tell them they should only rebuild during a mandatory (they can see this in our list here):
https://github.com/biblepay/biblepay/releases

[bible_pay]

Biblepay-Evolution is ready for testing in TestNet:


https://forum.biblepay.org/index.php?topic=391.msg5518#msg5518

More information on GSC's:
https://wiki.biblepay.org/Generic_Smart_Contracts

Roadmap:
https://wiki.biblepay.org/Roadmap


We could use at least 20 testers in testnet to test ABNs, GSCs, Deterministic Sancs, and we will also eventually need to test Evo in testnet against prod (meaning we need a few of us to sacrifice some capital and temporarily create DIP3 Sancs for prod in testnet for a couple months to ensure we are prod ready).

[MIP]

Biblepay-Evolution is ready for testing in TestNet:


https://forum.biblepay.org/index.php?topic=391.msg5518#msg5518

More information on GSC's:
https://wiki.biblepay.org/Generic_Smart_Contracts

Roadmap:
https://wiki.biblepay.org/Roadmap


We could use at least 20 testers in testnet to test ABNs, GSCs, Deterministic Sancs, and we will also eventually need to test Evo in testnet against prod (meaning we need a few of us to sacrifice some capital and temporarily create DIP3 Sancs for prod in testnet for a couple months to ensure we are prod ready).

MacOS version for testnet in
https://www.biblepay.org/biblepaycore-testnet.dmg

[togoshigekata]

AWESOME! Ill try and spin up a test node tonight!

[noxpost]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

[bible_pay]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

Its probably good that it finally came out in public anyway, as what is a little more redicules, is having people who claim to be *for* BBP secretly holding back so much anger and hatred, and consistently posting inaccurate info here on this board.

I always found it extremely disheartening to log into this board and see a page of hate, and I thought, what kind of intelligence does it take to bash our own Lead Dev, our own community and then expect the price to rise?  To hurt our orphans and to contribute negatively to our image.

At least in other communities Ive seen the common sense to keep negativity and personal views out of public discussions and proofread posts before clicking the POST button, not start public fights and create turmoil on a regular basis.

So hopefully you agree that this is all true also?

[noxpost]

Its probably good that it finally came out in public anyway, as what is a little more redicules, is having people who claim to be *for* BBP secretly holding back so much anger and hatred, and consistently posting inaccurate info here on this board.

I always found it extremely disheartening to log into this board and see a page of hate, and I thought, what kind of intelligence does it take to bash our own Lead Dev, our own community and then expect the price to rise?  To hurt our orphans and to contribute negatively to our image.

At least in other communities Ive seen the common sense to keep negativity and personal views out of public discussions and proofread posts before clicking the POST button, not start public fights and create turmoil on a regular basis.

So hopefully you agree that this is all true also?

I agree. I've posted several times about not wanting to come to this board to see vitriol, disagreements, bashing of the coin (or our team members, which OF COURSE includes you and MIP), or weird iamges of naked demon girls, or whatever.

I don't want to start a fight. I don't want to join a fight. I don't particularly care if there IS a fight, but I don't want the first thing that people see whenever they click any of our links to be a fight. Our Discord, our ANN thread, our exchanges, our reddit, whatever - let's keep it clean and on-mission.

For my PERSONAL perspective, in case I have confused or hurt anyone...

I've said it before and I'll say it again - I attach extremely significant value to the work Rob and MIP are doing, to the vision that they have, and to the dedication that they both bring to this project and the mission to carry God's word to the masses via our charity sponsorships and other features.

That's the bottom line, period. Anyone who understands anything different about my opinion is confused or wrong. If that's a situation I've created, then I thank you for bringing it to me and allowing me to clarify.

I don't mean this as "taking a side" - nobody is perfect. But if I didn't support the team and the mission, I wouldn't be here at all, and I'd like to think other people have the same option and the good sense to make the same choice.

Now people who genuinely care, and have issues/comments/concerns should be able to raise them in a RESPECTFUL way and get a RESPECTFUL answer. Nobody's perfect, and in many interactions between many different people (myself included, probably) there have been failures there on many sides. That's part of the human element, and moving past it is part of growth.

I for one refuse to join in any more of this - I'll talk about features, roadmaps, adoption, reports, transparency, and promotion. About gratitude and when necessary uncertainty. I commit myself to being a part of solidarity and growth and not division and anger.

[bible_pay]

Its probably good that it finally came out in public anyway, as what is a little more redicules, is having people who claim to be *for* BBP secretly holding back so much anger and hatred, and consistently posting inaccurate info here on this board.

I always found it extremely disheartening to log into this board and see a page of hate, and I thought, what kind of intelligence does it take to bash our own Lead Dev, our own community and then expect the price to rise?  To hurt our orphans and to contribute negatively to our image.

At least in other communities Ive seen the common sense to keep negativity and personal views out of public discussions and proofread posts before clicking the POST button, not start public fights and create turmoil on a regular basis.

So hopefully you agree that this is all true also?

I agree. I've posted several times about not wanting to come to this board to see vitriol, disagreements, bashing of the coin (or our team members, which OF COURSE includes you and MIP), or weird iamges of naked demon girls, or whatever.

I don't want to start a fight. I don't want to join a fight. I don't particularly care if there IS a fight, but I don't want the first thing that people see whenever they click any of our links to be a fight. Our Discord, our ANN thread, our exchanges, our reddit, whatever - let's keep it clean and on-mission.

For my PERSONAL perspective, in case I have confused or hurt anyone...

I've said it before and I'll say it again - I attach extremely significant value to the work Rob and MIP are doing, to the vision that they have, and to the dedication that they both bring to this project and the mission to carry God's word to the masses via our charity sponsorships and other features.

That's the bottom line, period. Anyone who understands anything different about my opinion is confused or wrong. If that's a situation I've created, then I thank you for bringing it to me and allowing me to clarify.

I don't mean this as "taking a side" - nobody is perfect. But if I didn't support the team and the mission, I wouldn't be here at all, and I'd like to think other people have the same option and the good sense to make the same choice.

Now people who genuinely care, and have issues/comments/concerns should be able to raise them in a RESPECTFUL way and get a RESPECTFUL answer. Nobody's perfect, and in many interactions between many different people (myself included, probably) there have been failures there on many sides. That's part of the human element, and moving past it is part of growth.

I for one refuse to join in any more of this - I'll talk about features, roadmaps, adoption, reports, transparency, and promotion. About gratitude and when necessary uncertainty. I commit myself to being a part of solidarity and growth and not division and anger.

Thanks brother Nox, I agree with you, and I am on board personally myself with replying in this way too (my replies on SX were actually born from love).

So what this really means for everyone, is we need to proofread our e-mails, texts, discords, PMs, everything - before we hit send.

To participate in this community I would like you to first check your information that you intend to spread, and verify every line of it is born OUT OF LOVE. 

Think:  WWJD .... 

Please dont call me a hyprocrite, because I repented for this days ago, and todays communication was born out of love.  Let's all do this.

[thesnat21]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

Totally agree.... 

I noticed before/after we lost 15m or so from the buy orders. 

[secoccular]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

Totally agree.... 

I noticed before/after we lost 15m or so from the buy orders. 

This should be highlighted. While we are indulging in bickering, real orders are being pulled. If we can set aside our pride for just a while...

[bible_pay]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

Totally agree.... 

I noticed before/after we lost 15m or so from the buy orders. 

This should be highlighted. While we are indulging in bickering, real orders are being pulled. If we can set aside our pride for just a while...

Exactly, I agree 100%.

[username_is_my_name]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

Full disclosure, nox just called me about 30 minutes ago and we had a real-life chat about this. I was actually a little convicted so I wanted to chime in.

I'm normally happy to get things out into the open, and heaven knows noxpost and I don't always agree (brothers are like that)...but yeah, I have to agree with this one. Whatever's going on, it won't help. I suspect if we were to dig into the root of the arguments I would land somewhere different than he does, but we can all agree public fighting is no bueno. Let's give it a rest. I don't care if it comes from a good place, a bad place, a weird place, a green place, just give it a rest.

If we don't agree we don't agree. I can think of lots of things I would like to change. I wouldn't take out a press release to talk about them or to air grievances though.

If for no other reasons, the price won't recover, and we won't be able to get any more good qualified people to help grow this. I think just about everyone here cares about at least one of those two things.

[bible_pay]

Not thrilled to log in to the SX exchange and see the entire chat log filled with fights between BBP community members. Seriously....as much as I'd love it if we'd STOP fighting, if we won't...could we at least contain it? Find a dedicated forum where everyone can get crabby with each other and keep that stuff off of public exchanges?

Here's a good rule - if it isn't news about the coin, it doesn't need to be on "external" sites.

Disagree with each other, with the plans, with the hearts of people or whatever else - if we must - but do it somewhere that non-BBP people won't see. This makes us look ridiculous.

Full disclosure, nox just called me about 30 minutes ago and we had a real-life chat about this. I was actually a little convicted so I wanted to chime in.

I'm normally happy to get things out into the open, and heaven knows noxpost and I don't always agree (brothers are like that)...but yeah, I have to agree with this one. Whatever's going on, it won't help. I suspect if we were to dig into the root of the arguments I would land somewhere different than he does, but we can all agree public fighting is no bueno. Let's give it a rest. I don't care if it comes from a good place, a bad place, a weird place, a green place, just give it a rest.

If we don't agree we don't agree. I can think of lots of things I would like to change. I wouldn't take out a press release to talk about them or to air grievances though.

If for no other reasons, the price won't recover, and we won't be able to get any more good qualified people to help grow this. I think just about everyone here cares about at least one of those two things.

Thanks, this is a good quality post with good advice.

Also, let's not hold grudges, Jesus commands us to forgive.

I think we should go forward and invite the Holy Spirit into each of our hearts.  The Holy Spirit will guide us to be positive and invite positive influences here.