kryptobean.eth

Also want to add this : @mr_benft has been in the weird position of not wanting to push me further into burnout, while catching heat for the issues. So go easy on him. I’ll get the bridge sorted, though I can’t give an ETA just yet.

So now that there's some new issues with the bridge, I have decided to redo the whole thing, and do it properly, which will take a bit of time. No assets will be lost, and I apologize for the inconvenience.

Here's an explanation about some of the issues with the bridge. When we launched the bridge, issues with the Solana network caused a lot of trouble. Nothing went through, and it was unclear at the time if the issue was with the bridge or with my code.

Let me defend my team member here : Kickr does all the graphic design and animation on all our websites, not just slapping together a psd, he does a lot of the html and css, and he does this better than any designer I’ve worked with. Not only that, he directs the video shoots, and is very much involved in the background daily, from art direction to strategy meetings, to designing logos and banners. We’re a small team, and a lot goes on at all times that you may not be aware of. You can disagree with things we do at times, but when you accuse Kickr (or Ben for that matter) of not doing much, I respectfully have to disagree. It’s just not accurate.

@kickRRR Type of response I expected from someone who hasn’t done shit in the last year and a half but show up to a fake photo shoot for a fake movie. Feel bad for @MemoAngeles_KB , you and @mr_benft are a terrible representation of his great artwork.

FYI, I have not been in our discord for over 1.5 years. I don’t even think anyone has noticed tbh. Discord is better of being community driven. A community is and will always be divided. It’s like politics, some red, some blue. People have different opinions on how things should be done and that’s fine. But what happens when you throw right wings in the same room as left wings. People who disagree with one and other. It causes a rift, and tbh an unnecessary rift within the community that 100% of the time continuous on the cl. I am in many different Killabears chats on X and they are great because they are grouped with people who share the same opinion and the vibes there are just so much better and healthier for everyone. This doesn’t mean there can’t be a Killabears discord, it just wont be us running it. NFTs is 100% community. No doubt about it, we’ve seen too many cases to say otherwise. If you don’t agree you are just being naive. As founders we are here to build and entertain, community comes with it.

We decided we're nuking the @killabearsnft discord in about a week. It's always had its pros and cons, but the negatives outweigh the positives by a longshot. There are plenty of community X groups for our holders to chat, and a recently created community created telegram chat. All official announcements once this happens will come through the official X account and on our website.

Glad we finally made it to Solana! Yesterday I was at the ER most of the day, due to a broken rib. Was a little worried it would mess up our launch (and so was @mr_benft, sorry for the panic attack), but managed to power through.

Building more cubs today. Shout out to big brained @KryptoBean for adding the Random button in the @killabearsnft cub builder. It's firing combos I never would have tried, and makes them so much quicker to build.

Friday night in the Cohen house… designing Cubs quickly thanks to @KryptoBean new RANDOM button 🎲

@SanestScientist To elaborate, if you burn too many volumes, you get kash. If you have kash, it selects to use that by default so you can burn less volumes. But if you burned the exact amount, the kash contract doesn’t get involved, it doesn’t need to increase or decrease your balance.

@SanestScientist The errors happened when KASH was involved. When burning the exact amount, it went through just fine. The permission on the KASH contract wasn’t set for the new burn market contract.

We had some technical issues with the last burn market, as some of you noticed. In order to get the goldens involved, we needed a new contract. The new contract was well tested and worked fine, but it needs to communicate with a couple of other contracts. This involves a series of transactions to link everything together. These transactions are handled by a deployment script. One of the txns that was needed didn’t make it when deploying. It wasn’t a failed transaction, it was probably an error when submitting it to the rpc that went unnoticed. This caused some issues when purchases involved KASH, and I had to pause the burn market while I was figuring things out. We have refunded all gas that was lost because of this.

The Hunt Is On...🔪🐻

@jed_131 @phantom In this case, it’s not actually a phantom integration, it was just the presence of the phantom plug-in breaking the cubs builder. It did something in a way similar to coinbase wallet (which I had support for), but slightly different, and that made things explode.

@KryptoBean Bean why do we need @phantom integration 👀😂😂😂 Trying to get alpha sorry 😂

@TheLoveCap @kickRRR Some stuff that is ready : - Rush soft staking - Scanner - Cub incubation / remix / unstaking - Bit equip / unequip - Cub bit boost - OE burning - Template designer - Linking wallets - Improved Discord role bot - Asset downloads - …

@TheLoveCap @kickRRR It’s in beta. Most utility is added (accessible directly from the assets page), but not everything is ready yet. We’re essentially condensing over a year of development into one platform.

Just claimed 17x RUSH in 2 clicks in the new dashboard. 1 - Quick Select > RUSH Claimable 2 - RUSH > Claim

#NewProfilePic @killabearsnft