--
-- Host: localhost    Database: poopcoin_nftmasterbox_db
-- ------------------------------------------------------


--
-- Table structure for table `dbt_blockchain_network`
--

CREATE TABLE `dbt_blockchain_network` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `network_name` varchar(100) DEFAULT NULL,
  `network_slug` varchar(100) DEFAULT NULL,
  `logo` varchar(255) DEFAULT NULL,
  `rpc_url` varchar(255) DEFAULT NULL,
  `chain_id` int(11) DEFAULT NULL,
  `currency_symbol` varchar(20) DEFAULT NULL,
  `explore_url` varchar(255) DEFAULT NULL,
  `port` int(11) DEFAULT NULL,
  `server_ip` varchar(22) DEFAULT NULL,
  `created_at` timestamp NULL DEFAULT CURRENT_TIMESTAMP,
  `created_by` int(11) DEFAULT NULL,
  `status` tinyint(4) NOT NULL DEFAULT '1',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_blockchain_network`
--

INSERT INTO `dbt_blockchain_network` VALUES (1,'Polygon','polygon',NULL,'https://polygon-rpc.com/',137,'MATIC','https://polygonscan.com/',81,'localhost','2022-08-03 01:11:28',NULL,1),(2,'Mumbai Testnet(Polygon)','polygon-testnet',NULL,'https://rpc-mumbai.maticvigil.com/',80001,'MATIC','https://mumbai.polygonscan.com/',81,'localhost','2022-08-03 01:12:27',NULL,0);

--
-- Table structure for table `dbt_contract_setup`
--

CREATE TABLE `dbt_contract_setup` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `contract_name` varchar(100) NOT NULL,
  `contract_symbol` varchar(50) NOT NULL,
  `max_token_supply` int(11) DEFAULT NULL,
  `contract_address` varchar(50) NOT NULL,
  `tnx_hash` varchar(128) NOT NULL,
  `status` int(11) NOT NULL COMMENT '0 = Inactive, 1 = Active',
  `network_id` int(11) DEFAULT NULL,
  `create_at` datetime DEFAULT NULL,
  `update_at` datetime DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_contract_setup`
--

INSERT INTO `dbt_contract_setup` VALUES (2,'NFTMASTERBOX','NMB',1000000,'0xAfe3DAcF7C0573CF59F2Bb3f6Ec55659b482D014','0x734692dbce7ca4e2500c4bca8d8fc6e0a0e2bb7f66526952682879209bb2f5a2',1,1,'2024-03-23 05:21:20',NULL);

--
-- Table structure for table `dbt_earnings`
--

CREATE TABLE `dbt_earnings` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nft_id` int(11) DEFAULT NULL,
  `user_id` varchar(20) DEFAULT NULL,
  `txn_type` varchar(20) DEFAULT NULL,
  `amount` float(22,8) DEFAULT NULL,
  `tnx_info` longtext CHARACTER SET utf8,
  `created_at` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `dbt_earnings`
--


--
-- Table structure for table `dbt_envato_purchase_info`
--

CREATE TABLE `dbt_envato_purchase_info` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `product_key` varchar(100) NOT NULL,
  `purchase_key` varchar(100) NOT NULL,
  `sold_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `supported_until` timestamp NULL DEFAULT NULL,
  `item_name` varchar(500) NOT NULL,
  `item_id` varchar(50) NOT NULL,
  `create_at` datetime DEFAULT CURRENT_TIMESTAMP,
  `update_at` datetime DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `dbt_envato_purchase_info`
--

INSERT INTO `dbt_envato_purchase_info` VALUES (2,'38375099','318032ec-9091-4c2a-9a3b-da8cade01ccd','2024-03-23 11:11:58','2024-09-22 01:11:58','NFTBOX - NFT Marketplace Script','38375099','2024-03-22 18:45:33',NULL);

--
-- Table structure for table `dbt_external_api_setup`
--

CREATE TABLE `dbt_external_api_setup` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(50) NOT NULL,
  `data` text NOT NULL,
  `status` tinyint(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_external_api_setup`
--

INSERT INTO `dbt_external_api_setup` VALUES (4,'Google Map API','{\"api_key\":\"AIzaSyAUmj7I0GuGJWRcol-pMUmM4rrnHS90DE8\"}',1);

--
-- Table structure for table `dbt_favorite_items`
--

CREATE TABLE `dbt_favorite_items` (
  `fv_id` int(11) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(12) DEFAULT NULL,
  `nft_id` int(11) DEFAULT NULL,
  `network_id` int(11) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  PRIMARY KEY (`fv_id`),
  KEY `fv_id` (`fv_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_favorite_items`
--


--
-- Table structure for table `dbt_fees_tbl`
--

CREATE TABLE `dbt_fees_tbl` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `level` text,
  `fees` float DEFAULT NULL,
  `status` int(11) NOT NULL DEFAULT '1',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_fees_tbl`
--


--
-- Table structure for table `dbt_file_gateway`
--

CREATE TABLE `dbt_file_gateway` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `gateway_name` varchar(55) DEFAULT NULL,
  `api_key` varchar(255) DEFAULT NULL,
  `secret_key` varchar(255) DEFAULT NULL,
  `end_point` varchar(255) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_file_gateway`
--


--
-- Table structure for table `dbt_language`
--

CREATE TABLE `dbt_language` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `phrase` text NOT NULL,
  `english` text,
  `french` text,
  `korean` text,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=995 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_language`
--



--
-- Table structure for table `dbt_module`
--

CREATE TABLE `dbt_module` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(50) NOT NULL,
  `description` text,
  `image` varchar(255) DEFAULT NULL,
  `directory` varchar(100) DEFAULT NULL,
  `status` tinyint(1) NOT NULL DEFAULT '1',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_module`
--


--
-- Table structure for table `dbt_nft_biding`
--

CREATE TABLE `dbt_nft_biding` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nft_listing_id` int(11) DEFAULT NULL,
  `nft_id` int(11) DEFAULT NULL,
  `bid_from_id` varchar(11) DEFAULT NULL,
  `bid_start_at` datetime DEFAULT NULL,
  `bid_end_at` datetime DEFAULT NULL,
  `bid_amount` double(22,8) DEFAULT NULL,
  `status` tinyint(4) DEFAULT '1' COMMENT '1 = active, 2 = success, 3=expired, 4 =canceld',
  `accept_status` tinyint(4) DEFAULT '0',
  `cancel_status` tinyint(4) NOT NULL DEFAULT '0',
  `created_at` datetime DEFAULT NULL,
  `created_by` varchar(22) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_biding`
--


--
-- Table structure for table `dbt_nft_biding_log`
--

CREATE TABLE `dbt_nft_biding_log` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nft_bid_id` int(11) DEFAULT NULL,
  `nft_listing_id` int(11) DEFAULT NULL,
  `nft_id` int(11) DEFAULT NULL,
  `bid_from_id` int(11) DEFAULT NULL,
  `bid_start_at` datetime DEFAULT NULL,
  `bid_end_at` datetime DEFAULT NULL,
  `bid_amount` double(22,8) DEFAULT NULL,
  `status` tinyint(4) DEFAULT '1',
  `cancel_status` tinyint(4) DEFAULT '0',
  `accept_status` tinyint(4) DEFAULT '0',
  `created_at` datetime DEFAULT NULL,
  `created_by` varchar(22) DEFAULT NULL,
  `updated_at` timestamp NULL DEFAULT CURRENT_TIMESTAMP,
  `updated_by` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_biding_log`
--


--
-- Table structure for table `dbt_nft_category`
--

CREATE TABLE `dbt_nft_category` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `cat_name` varchar(20) DEFAULT NULL,
  `slug` varchar(255) DEFAULT NULL,
  `description` varchar(255) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  `created_by` int(11) DEFAULT NULL,
  `status` tinyint(4) DEFAULT NULL,
  `logo` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_category`
--

INSERT INTO `dbt_nft_category` VALUES (1,'ART','art','',NULL,NULL,1,'/public/uploads/category/logo/1655206226_73232f5f1fdbe556a570.jpg');

--
-- Table structure for table `dbt_nft_collection`
--

CREATE TABLE `dbt_nft_collection` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(22) DEFAULT NULL,
  `title` varchar(255) DEFAULT NULL,
  `slug` varchar(255) DEFAULT NULL,
  `description` varchar(255) DEFAULT NULL,
  `category_id` int(11) DEFAULT NULL,
  `status` tinyint(4) DEFAULT NULL,
  `logo_image` varchar(255) DEFAULT NULL,
  `banner_image` varchar(255) DEFAULT NULL,
  `created_at` timestamp NULL DEFAULT CURRENT_TIMESTAMP,
  `created_by` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_collection`
--


--
-- Table structure for table `dbt_nft_listing`
--

CREATE TABLE `dbt_nft_listing` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `nft_store_id` int(11) DEFAULT NULL,
  `nft_token_id` varchar(55) DEFAULT NULL,
  `list_from` varchar(22) DEFAULT NULL,
  `auction_type` varchar(10) DEFAULT NULL COMMENT 'bid / fixed',
  `approve_type` tinyint(4) NOT NULL DEFAULT '1' COMMENT '2=automatic,1=manual',
  `min_price` double(22,8) DEFAULT NULL,
  `max_price` double(22,8) DEFAULT NULL,
  `reserve_price` double(22,8) DEFAULT NULL,
  `start_date` datetime DEFAULT NULL,
  `end_date` datetime DEFAULT NULL,
  `status` tinyint(4) DEFAULT '0' COMMENT '0=on sale, 1=sale success, 2=expired, 3=canceled',
  `total_bid` int(11) NOT NULL DEFAULT '0',
  `created_at` datetime DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_listing`
--


--
-- Table structure for table `dbt_nft_listing_log`
--

CREATE TABLE `dbt_nft_listing_log` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `listing_id` int(11) DEFAULT NULL,
  `nft_store_id` int(11) DEFAULT NULL,
  `nft_token_id` varchar(55) DEFAULT NULL,
  `list_from` varchar(22) DEFAULT NULL,
  `auction_type` varchar(10) DEFAULT NULL COMMENT 'bid / fixed',
  `approve_type` tinyint(4) NOT NULL DEFAULT '1' COMMENT '2=automatic,1=manual',
  `min_price` double(22,8) DEFAULT NULL,
  `max_price` double(22,8) DEFAULT NULL,
  `reserve_price` double(22,8) DEFAULT NULL,
  `start_date` date DEFAULT NULL,
  `end_date` date DEFAULT NULL,
  `status` tinyint(4) DEFAULT '0' COMMENT '0=on sale, 1=sale success, 2=expired, 3=canceled',
  `total_bid` int(11) NOT NULL DEFAULT '0',
  `created_at` datetime DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  `trx_info` longtext,
  `buyer_id` varchar(20) DEFAULT NULL,
  `buyer_wallet` varchar(100) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_listing_log`
--


--
-- Table structure for table `dbt_nft_selling_type`
--

CREATE TABLE `dbt_nft_selling_type` (
  `type_id` int(11) NOT NULL AUTO_INCREMENT,
  `type` varchar(11) DEFAULT NULL,
  `status` tinyint(4) DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  PRIMARY KEY (`type_id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_selling_type`
--

INSERT INTO `dbt_nft_selling_type` VALUES (1,'Bid',1,'2022-02-10 17:37:53'),(2,'Fix',1,'2022-02-10 17:37:53');

--
-- Table structure for table `dbt_nft_transfer_option`
--

CREATE TABLE `dbt_nft_transfer_option` (
  `option_id` int(11) NOT NULL AUTO_INCREMENT,
  `option` varchar(22) DEFAULT NULL,
  `status` tinyint(4) DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  PRIMARY KEY (`option_id`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nft_transfer_option`
--

INSERT INTO `dbt_nft_transfer_option` VALUES (1,'Internal Transfer',1,'2022-02-14 13:28:03'),(2,'Extarnal Transfer',1,'2022-02-14 13:28:03');

--
-- Table structure for table `dbt_nft_transfer_queue`
--

CREATE TABLE `dbt_nft_transfer_queue` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(100) NOT NULL,
  `nft_id` varchar(100) NOT NULL,
  `from_wallet` varchar(50) CHARACTER SET utf8 NOT NULL COMMENT 'User wallet',
  `to_wallet` varchar(50) CHARACTER SET utf8 NOT NULL COMMENT 'Admin wallet',
  `trx` date DEFAULT NULL,
  `price` double(22,8) DEFAULT NULL,
  `comment` varchar(255) DEFAULT NULL,
  `status` tinyint(1) NOT NULL COMMENT '2 = Pending, 1 = Success, 0 = Cancel, 3 = Tnx Hash pending, 4 = Tnx Pause, 5 = GAS sending',
  `request_time` datetime DEFAULT NULL,
  `success_time` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_nft_transfer_queue`
--


--
-- Table structure for table `dbt_nfts_store`
--

CREATE TABLE `dbt_nfts_store` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(11) DEFAULT NULL,
  `owner_wallet` varchar(50) DEFAULT NULL,
  `name` varchar(255) DEFAULT NULL,
  `contract_address` varchar(255) DEFAULT NULL,
  `token_id` varchar(200) DEFAULT NULL,
  `token_standard` varchar(10) DEFAULT NULL,
  `blockchain_id` int(11) DEFAULT NULL,
  `file_token` varchar(255) DEFAULT NULL,
  `file_uri` varchar(255) DEFAULT NULL,
  `file` varchar(255) DEFAULT NULL,
  `description` longtext,
  `metatag` text COMMENT 'tag1,tag2',
  `properties` text,
  `category_id` int(11) DEFAULT NULL,
  `collection_id` int(11) DEFAULT NULL,
  `is_minted` tinyint(4) NOT NULL DEFAULT '0' COMMENT '1=yes, 0 = no',
  `trx_hash` varchar(155) DEFAULT NULL,
  `status` tinyint(4) DEFAULT '2' COMMENT '0 = pending, 1 = active, 2 = Suspend, 3 = on sell',
  `is_verified` tinyint(4) NOT NULL DEFAULT '0' COMMENT '0=un_verified, 1=verified',
  `price` double(22,8) DEFAULT '0.00000000',
  `is_featured` tinyint(4) DEFAULT NULL,
  `suspend_msg` text,
  `created_at` datetime DEFAULT NULL,
  `created_by` varchar(22) DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nfts_store`
--


--
-- Table structure for table `dbt_nfts_store_log`
--

CREATE TABLE `dbt_nfts_store_log` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `store_id` int(11) DEFAULT NULL,
  `user_id` varchar(11) DEFAULT NULL,
  `owner_wallet` varchar(50) DEFAULT NULL,
  `name` varchar(255) DEFAULT NULL,
  `contract_address` varchar(255) DEFAULT NULL,
  `token_id` varchar(200) DEFAULT NULL,
  `token_standard` varchar(10) DEFAULT NULL,
  `blockchain_id` int(11) DEFAULT NULL,
  `file_token` varchar(255) DEFAULT NULL,
  `file_uri` varchar(255) DEFAULT NULL,
  `file` varchar(255) DEFAULT NULL,
  `description` varchar(255) DEFAULT NULL,
  `metatag` text COMMENT 'tag1,tag2',
  `properties` longtext,
  `category_id` int(11) DEFAULT NULL,
  `collection_id` int(11) DEFAULT NULL,
  `is_minted` tinyint(4) NOT NULL DEFAULT '0' COMMENT '1=yes, 0 = no',
  `trx_hash` varchar(155) DEFAULT NULL,
  `trx` longtext,
  `status` tinyint(4) DEFAULT '2' COMMENT '0 = pending, 1 = active, 2 = Suspend, 3 = on sell',
  `ownership` varchar(12) DEFAULT NULL,
  `is_verified` tinyint(4) NOT NULL DEFAULT '0' COMMENT '0=un_verified, 1=verified',
  `is_featured` tinyint(4) DEFAULT '0',
  `price` double(22,8) DEFAULT '0.00000000',
  `suspend_msg` text,
  `created_at` datetime DEFAULT NULL,
  `created_by` varchar(22) DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_nfts_store_log`
--


--
-- Table structure for table `dbt_setting`
--

CREATE TABLE `dbt_setting` (
  `setting_id` int(11) NOT NULL AUTO_INCREMENT,
  `title` varchar(255) DEFAULT NULL,
  `description` text,
  `email` varchar(50) DEFAULT NULL,
  `phone` varchar(20) DEFAULT NULL,
  `logo` varchar(255) DEFAULT NULL,
  `logo_web` varchar(255) NOT NULL,
  `header_bg_img` varchar(255) DEFAULT NULL,
  `footer_bg_img` varchar(255) DEFAULT NULL,
  `favicon` varchar(255) DEFAULT NULL,
  `language` varchar(100) DEFAULT NULL,
  `site_align` varchar(50) DEFAULT NULL,
  `footer_text` varchar(255) DEFAULT NULL,
  `time_zone` varchar(100) DEFAULT NULL,
  `latitude` varchar(100) DEFAULT NULL,
  `office_time` varchar(255) DEFAULT NULL,
  `update_notification` varchar(255) NOT NULL,
  PRIMARY KEY (`setting_id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_setting`
--

INSERT INTO `dbt_setting` VALUES (1,'NFTMASTERBOX','','contacts@nftmasterbox.com','','/public/uploads/settings/1652779987_ec0e30b82f1bcd0a4209.png','/public/uploads/settings/1652779939_21b53479397d6c74fcb6.png','/public/uploads/settings/1655382014_6efbe1f35652a8b025b0.png','/public/uploads/settings/1655382940_681b42aa9daebb9d91f9.jpg','/public/uploads/dashboard/1652779939_8694a944f0e536e4527e.png','english','LTR','2024 © Copyright nftmasterbox.com','Asia/Dubai','','','1');

--
-- Table structure for table `dbt_sms_email_send_setup`
--

CREATE TABLE `dbt_sms_email_send_setup` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `method` text NOT NULL,
  `deposit` int(11) DEFAULT NULL,
  `transfer` int(11) DEFAULT NULL,
  `withdraw` int(11) DEFAULT NULL,
  `payout` int(11) DEFAULT NULL,
  `commission` int(11) DEFAULT NULL,
  `team_bonnus` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_sms_email_send_setup`
--


--
-- Table structure for table `dbt_sms_email_template`
--

CREATE TABLE `dbt_sms_email_template` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `sms_or_email` varchar(10) NOT NULL,
  `template_name` varchar(50) NOT NULL,
  `subject_en` varchar(300) NOT NULL,
  `subject_fr` varchar(300) NOT NULL,
  `template_en` varchar(300) NOT NULL,
  `template_fr` varchar(300) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=21 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_sms_email_template`
--

INSERT INTO `dbt_sms_email_template` VALUES (20,'email','registration','Verify Your Account - NFTBOX','','Hello %fullname% \r\nYour account was created successfully, Please click on the link below to activate your account. ','<br><b>Votre compte a été créé avec succès, veuillez cliquer sur le lien ci-dessous pour activer votre compte. </b>');

--
-- Table structure for table `dbt_social_link`
--

CREATE TABLE `dbt_social_link` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(100) NOT NULL,
  `link` varchar(100) NOT NULL,
  `icon` varchar(100) NOT NULL,
  `status` int(11) NOT NULL,
  `date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_social_link`
--

INSERT INTO `dbt_social_link` VALUES (1,'Facebook','https://www.facebook.com','facebook',1,'2018-04-02 01:52:31'),(2,'twitter','https://twitter.com','twitter',1,'2018-04-02 01:29:25'),(3,'google plus','https://google-plus.com','google-plus',1,'2018-01-31 19:58:56'),(4,'youtube','https://www.youtube.com','youtube-play',1,'2018-04-02 01:28:49'),(5,'instagram','https://instagram.com','instagram',1,'2018-01-31 19:58:56');

--
-- Table structure for table `dbt_themes`
--

CREATE TABLE `dbt_themes` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) NOT NULL,
  `status` tinyint(4) NOT NULL,
  `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_themes`
--

INSERT INTO `dbt_themes` VALUES (1,'website_template',1,'2021-01-14 11:14:07','2021-06-15 11:37:10');

--
-- Table structure for table `dbt_user`
--

CREATE TABLE `dbt_user` (
  `uid` int(11) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(20) DEFAULT NULL,
  `username` varchar(20) DEFAULT NULL,
  `sponsor_id` varchar(20) DEFAULT NULL,
  `lang` varchar(50) DEFAULT 'english',
  `f_name` varchar(50) DEFAULT NULL,
  `l_name` varchar(50) DEFAULT NULL,
  `bio` text,
  `email` varchar(100) DEFAULT NULL,
  `phone` varchar(20) DEFAULT NULL,
  `image` text,
  `banner_image` varchar(255) DEFAULT NULL,
  `address` varchar(255) DEFAULT NULL,
  `gender` varchar(10) DEFAULT NULL,
  `country` varchar(20) DEFAULT NULL,
  `password` varchar(50) DEFAULT NULL,
  `password_reset_tocken` longtext,
  `reg_ip` varchar(255) DEFAULT NULL,
  `status` tinyint(1) NOT NULL DEFAULT '1' COMMENT '0=did not active acc, 1= activated, 2 = deactivated , 3 = suspend',
  `is_verified` tinyint(4) DEFAULT NULL,
  `created` datetime DEFAULT NULL,
  `modified` datetime DEFAULT NULL,
  `portfolio_url` varchar(255) DEFAULT NULL,
  `wallet_address` varchar(255) DEFAULT NULL,
  `chain_id` int(11) DEFAULT NULL,
  PRIMARY KEY (`uid`),
  UNIQUE KEY `user_id_UNIQUE` (`user_id`),
  UNIQUE KEY `email_UNIQUE` (`email`),
  UNIQUE KEY `username` (`username`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='All user information will be stored into this table.';

--
-- Dumping data for table `dbt_user`
--


--
-- Table structure for table `dbt_user_account`
--

CREATE TABLE `dbt_user_account` (
  `ac_id` int(11) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(11) DEFAULT NULL,
  `currency_id` int(11) DEFAULT NULL,
  `symbol` varchar(11) DEFAULT NULL,
  `balance` double(22,8) DEFAULT NULL,
  `hold_balance` decimal(22,8) DEFAULT NULL,
  `comment` varchar(255) DEFAULT NULL,
  `created_by` int(11) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  PRIMARY KEY (`ac_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_user_account`
--


--
-- Table structure for table `dbt_user_transaction`
--

CREATE TABLE `dbt_user_transaction` (
  `tr_id` int(11) NOT NULL AUTO_INCREMENT,
  `user_id` varchar(11) DEFAULT NULL,
  `currency_id` int(11) DEFAULT NULL,
  `symbol` varchar(11) DEFAULT NULL,
  `transaction_type_id` int(11) DEFAULT NULL COMMENT 'transaction_type table id',
  `transaction_type` varchar(22) DEFAULT NULL COMMENT 'Diposit/Withdraw/Transfer etc',
  `transaction_method` varchar(22) DEFAULT NULL COMMENT 'Stripe/Paypal/Admin etc',
  `fees` double(22,8) DEFAULT NULL,
  `amount` double(22,8) DEFAULT NULL,
  `to_wallet` varchar(100) DEFAULT NULL,
  `status` varchar(22) DEFAULT NULL,
  `trx_info` longtext,
  `created_by` int(11) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  `trx` longtext,
  PRIMARY KEY (`tr_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_user_transaction`
--


--
-- Table structure for table `dbt_web_article`
--

CREATE TABLE `dbt_web_article` (
  `article_id` int(11) NOT NULL AUTO_INCREMENT,
  `slug` varchar(100) DEFAULT NULL,
  `headline_en` varchar(300) NOT NULL,
  `article_image` varchar(100) DEFAULT NULL,
  `custom_url` varchar(300) NOT NULL,
  `article1_en` longtext NOT NULL,
  `article2_en` longtext NOT NULL,
  `video` varchar(300) DEFAULT NULL,
  `cat_id` int(11) DEFAULT NULL,
  `page_content` int(11) DEFAULT '0' COMMENT 'if this is a Page content set 1 else 0',
  `position_serial` int(11) NOT NULL,
  `publish_date` datetime NOT NULL,
  `publish_by` varchar(25) NOT NULL,
  `edit_history` int(11) NOT NULL,
  PRIMARY KEY (`article_id`),
  UNIQUE KEY `slug` (`slug`)
) ENGINE=InnoDB AUTO_INCREMENT=19 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_web_article`
--

INSERT INTO `dbt_web_article` VALUES (1,NULL,'Big market for',NULL,'','Mint, Buy, and Sell Your NFT\'s\r\n','NFTBOX is the biggest Blockchain based NFT marketplace','',1,1,1,'2022-07-06 10:36:33','nftbox@demo.com',0),(2,NULL,'About Us','','','Personal identification information\r\nWe may collect personal identification information from Users in a variety of ways, including, but not limited to, when Users visit our site, register on the site, and in connection with other activities, services, features or resources we make available on our Site. Users may be asked for, as appropriate, name, email address, mailing address, phone number. Users may, however, visit our Site anonymously. We will collect personal identification information from Users only if they voluntarily submit such information to us. Users can always refuse to supply personally identification information, except that it may prevent them from engaging in certain Site related activities.\r\n\r\nNon-personal identification information\r\nWe may collect non-personal identification information about Users whenever they interact with our Site. Non-personal identification information may include the browser name, the type of computer and technical information about Users means of connection to our Site, such as the operating system and the Internet service providers utilized and other similar information.\r\n\r\nWeb browser cookies\r\nOur Site may use &#34;cookies&#34; to enhance User experience. User&#39;s web browser places cookies on their hard drive for record-keeping purposes and sometimes to track information about them. User may choose to set their web browser to refuse cookies, or to alert you when cookies are being sent. If they do so, note that some parts of the Site may not function properly.','<h3 style=\"margin: 15px 0px; padding: 0px; font-weight: 700; font-size: 14px; font-family: &quot;Open Sans&quot;, Arial, sans-serif;\">The standard Lorem Ipsum passage, used since the 1500s</h3><p style=\"margin-right: 0px; margin-bottom: 15px; margin-left: 0px; padding: 0px; text-align: justify; font-family: &quot;Open Sans&quot;, Arial, sans-serif;\"><strong style=\"margin: 0px; padding: 0px;\">Lorem Ipsum</strong>&nbsp;is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p><h3 style=\"margin: 15px 0px; font-weight: 700; font-size: 14px; padding: 0px; font-family: &quot;Open Sans&quot;, Arial, sans-serif;\">Lorem Ipsum passage is the best placeholder.</h3><p style=\"margin-right: 0px; margin-bottom: 15px; margin-left: 0px; padding: 0px; text-align: justify; font-family: &quot;Open Sans&quot;, Arial, sans-serif;\">\"Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.\"</p><h3 style=\"margin: 15px 0px; font-weight: 700; font-size: 14px; padding: 0px; font-family: &quot;Open Sans&quot;, Arial, sans-serif;\">This could be the best Lorem Ipsum passage yet.</h3><p style=\"margin-right: 0px; margin-bottom: 15px; margin-left: 0px; padding: 0px; text-align: justify; font-family: &quot;Open Sans&quot;, Arial, sans-serif;\"><span style=\"font-weight: bolder; margin: 0px; padding: 0px;\">Lorem Ipsum</span>&nbsp;is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p>','https://www.youtube.com/watch?v=bWW5Kz2bEPg',2,1,1,'2022-06-14 10:42:30','admin@demo.com',0),(3,'terms','Lorem Ipsum','public/uploads/team/59f4a8b127a56d2f3eac2ba3d537175d.png','','It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout.','<p>Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry\'s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p>',NULL,5,0,1,'2022-05-29 11:37:05','bdtask@gmail.com',0),(5,NULL,'Repellat Odit Aliquid?',NULL,'','Lorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit, ipsum, fuga, in, obcaecati magni ullam nobis voluptas fugiat tenetur voluptatum quas tempora maxime rerum neque deserunt suscipit provident cumque et mollitia ex aspernatur porro minus sapiente voluptatibus eos at perferendis repellat odit aliquid harum molestias ratione pariatur adipisci. Aliquid, iure.','',NULL,3,0,0,'2018-04-08 10:43:08','admin@demo.com',0),(6,NULL,'Repellat Odit Aliquid?',NULL,'','Lorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit, ipsum, fuga, in, obcaecati magni ullam nobis voluptas fugiat tenetur voluptatum quas tempora maxime rerum neque deserunt suscipit provident cumque et mollitia ex aspernatur porro minus sapiente voluptatibus eos at perferendis repellat odit aliquid harum molestias ratione pariatur adipisci. ','',NULL,3,0,0,'2021-06-16 04:15:34','rdmvaijah@gmail.com',0),(7,'LatLng','Lat Lng',NULL,'','40.6700','-73.9400',NULL,4,0,0,'2022-05-17 10:46:00','bdtask@gmail.com',0),(8,'privacy','Privacy policy, terms and conditions','//public/uploads/e6f91e805b1cdd3139809fa748ebb25c.pdf','','<p class=\"bd-lead\">This Privacy Policy governs the manner in which NFT collects, uses, maintains and\r\n                discloses information collected from users (each, a \"User\") of the http://www.NFT.com website\r\n                (\"Site\").</p>\r\n\r\n              <h2>Personal identification information</h2>\r\n              <p>We may collect personal identification information from Users in a variety of ways, including, but not\r\n                limited to, when Users visit our site, register on the site, and in connection with other activities,\r\n                services, features or resources we make available on our Site. Users may be asked for, as appropriate,\r\n                name, email address, mailing address, phone number. Users may, however, visit our Site anonymously. We\r\n                will collect personal identification information from Users only if they voluntarily submit such\r\n                information to us. Users can always refuse to supply personally identification information, except that\r\n                it may prevent them from engaging in certain Site related activities.</p>\r\n\r\n\r\n              <h3>Non-personal identification information</h3>\r\n              <p>We may collect non-personal identification information about Users whenever they interact with our\r\n                Site. Non-personal identification information may include the browser name, the type of computer and\r\n                technical information about Users means of connection to our Site, such as the operating system and the\r\n                Internet service providers utilized and other similar information.</p>\r\n\r\n\r\n              <h3>Web browser cookies</h3>\r\n              <p>Our Site may use \"cookies\" to enhance User experience. User\'s web browser places cookies on their hard\r\n                drive for record-keeping purposes and sometimes to track information about them. User may choose to set\r\n                their web browser to refuse cookies, or to alert you when cookies are being sent. If they do so, note\r\n                that some parts of the Site may not function properly.</p>\r\n\r\n              <h3>How we use collected information</h3>\r\n              <p>NFT may collect and use Users personal information for the following purposes:</p>\r\n              <ul class=\"list-checked mb-9 mb-md-10\">\r\n                <li>To run and operate our Site We may need your information display content on the Site correctly.</li>\r\n                <li>To improve customer service\r\n                  Information you provide helps us respond to your customer service requests and support needs more\r\n                  efficiently.</li>\r\n                <li>To personalize user experience\r\n                  We may use information in the aggregate to understand how our Users as a group use the services and\r\n                  resources provided on our Site.</li>\r\n                <li>To improve our Site\r\n                  We may use feedback you provide to improve our products and services.</li>\r\n                <li>To run a promotion, contest, survey or other Site feature\r\n                  To send Users information they agreed to receive about topics we think will be of interest to them.\r\n                </li>\r\n                <li>To send periodic emails\r\n                  We may use the email address to send User information and updates pertaining to their order. It may\r\n                  also be used to respond to their inquiries, questions, and/or other requests.</li>\r\n              </ul>\r\n              <h3>How we protect your information</h3>\r\n              <p>We adopt appropriate data collection, storage and processing practices and security measures to protect\r\n                against unauthorized access, alteration, disclosure or destruction of your personal information,\r\n                username, password, transaction information and data stored on our Site.</p>\r\n\r\n              <!--<h3>Sharing your personal information</h3>\r\n                          <p>We may share or sell information with third parties for marketing or other purposes.</p>-->\r\n\r\n              <h3>Electronic newsletters</h3>\r\n              <p>If User decides to opt-in to our mailing list, they will receive emails that may include company news,\r\n                updates, related product or service information, etc.</p>\r\n\r\n              <h3>Advertising</h3>\r\n              <p>Ads appearing on our site may be delivered to Users by advertising partners, who may set cookies. These\r\n                cookies allow the ad server to recognize your computer each time they send you an online advertisement\r\n                to compile non personal identification information about you or others who use your computer. This\r\n                information allows ad networks to, among other things, deliver targeted advertisements that they believe\r\n                will be of most interest to you. This privacy policy does not cover the use of cookies by any\r\n                advertisers.</p>\r\n\r\n              <h3>Google Adsense</h3>\r\n              <p>Some of the ads may be served by Google. Google\'s use of the DART cookie enables it to serve ads to\r\n                Users based on their visit to our Site and other sites on the Internet. DART uses \"non personally\r\n                identifiable information\" and does NOT track personal information about you, such as your name, email\r\n                address, physical address, etc. You may opt out of the use of the DART cookie by visiting the Google ad\r\n                and content network privacy policy at <a\r\n                  href=\"https://www.google.com/privacy_ads.html\">http://www.google.com/privacy_ads.html</a></p>\r\n\r\n','              <h3>Changes to this privacy policy</h3>\r\n              <p>NFT has the discretion to update this privacy policy at any time. When we do, we will post a\r\n                notification on the main page of our Site. We encourage Users to frequently check this page for any\r\n                changes to stay informed about how we are helping to protect the personal information we collect. You\r\n                acknowledge and agree that it is your responsibility to review this privacy policy periodically and\r\n                become aware of modifications.</p>\r\n\r\n              <h3>Your acceptance of these terms</h3>\r\n              <p>By using this Site, you signify your acceptance of this policy. If you do not agree to this policy,\r\n                please do not use our Site. Your continued use of the Site following the posting of changes to this\r\n                policy will be deemed your acceptance of those changes. </p>\r\n\r\n              <h3>Contacting us</h3>\r\n              <p>If you have any questions about this Privacy Policy, the practices of this site, or your dealings with\r\n                this site, please contact us.</p>\r\n\r\n              <p>This document was last updated on August 21, 2016</p>','',6,1,1,'2022-06-08 06:55:58','admin@demo.com',0),(9,NULL,'Repellat Odit Aliquid?',NULL,'','Lorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit, ipsum, fuga, in, obcaecati magni ullam nobis voluptas fugiat tenetur voluptatum quas tempora maxime rerum neque deserunt suscipit provident cumque et mollitia ex aspernatur porro minus sapiente voluptatibus eos at perferendis repellat odit aliquid harum molestias ratione pariatur adipisci. Aliquid, iure. update','',NULL,3,0,0,'2022-06-08 06:56:33','admin@demo.com',0),(10,NULL,'What is goal?',NULL,'','Lorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit, ipsum, fuga, in, obcaecati magni ullam nobis voluptas fugiat tenetur voluptatum quas tempora maxime rerum neque deserunt suscipit provident cumque et mollitia ex aspernatur porro minus sapiente voluptatibus eos at perferendis repellat odit aliquid harum molestias ratione pariatur adipisci. ','',NULL,3,0,0,'2022-05-17 11:01:22','bdtask@gmail.com',0),(11,'msgus','Message Us',NULL,'','MESSAGE US','Start a chat!',NULL,4,0,0,'2022-05-17 10:45:48','bdtask@gmail.com',0),(12,'callanytime','Call Anytime',NULL,'','CALL ANYTIME','+8801558177887',NULL,4,0,0,'0000-00-00 00:00:00','',0),(13,'emailus','Email Us',NULL,'','EMAIL US','support@NFT.com',NULL,4,0,0,'2022-05-17 10:45:39','bdtask@gmail.com',0),(14,'letus','Let Us',NULL,'','Let us hear from you directly!','Our guests always travel the world in style. Mention @Bdtask<br> on Instagram for a chance to be featured!',NULL,4,0,0,'2022-05-17 10:45:32','bdtask@gmail.com',0),(15,'address','Address',NULL,'','Address','Bangladesh Office<br>                   B-25, Mannan Plaza, 4th Floor, Khilkhet<br>                   Dhaka-1229, Bangladesh',NULL,4,0,0,'0000-00-00 00:00:00','',0),(16,'phone_whatsapp','Connect Our WhatsApp',NULL,'','Phone & WhatsApp Number','+8801558177887<br>                 +8801817584639',NULL,4,0,0,'2022-05-17 10:46:50','bdtask@gmail.com',0),(17,'email','Email Address',NULL,'','Email','bdtask@gmail.com <br>                 support@NFT.com',NULL,4,0,0,'2022-06-14 05:36:17','a@a.com',0),(18,NULL,'What is Lorem Ipsum?',NULL,'','Lorem ipsum dolor sit amet, consectetur adipisicing elit. Reprehenderit, ipsum, fuga, in, obcaecati magni ullam nobis voluptas fugiat tenetur voluptatum quas tempora maxime rerum neque deserunt suscipit provident cumque et mollitia ex aspernatur porro minus sapiente voluptatibus eos at perferendis repellat odit aliquid harum molestias ratione pariatur adipisci. Aliquid, iure.','',NULL,3,0,0,'2022-06-08 06:56:56','admin@demo.com',0);

--
-- Table structure for table `dbt_web_category`
--

CREATE TABLE `dbt_web_category` (
  `cat_id` int(11) NOT NULL AUTO_INCREMENT,
  `slug` varchar(100) NOT NULL,
  `cat_name_en` varchar(100) NOT NULL,
  `parent_id` int(11) NOT NULL,
  `cat_image` varchar(300) DEFAULT NULL,
  `cat_title1_en` varchar(100) DEFAULT NULL,
  `cat_title2_en` varchar(300) DEFAULT NULL,
  `menu` int(11) NOT NULL COMMENT 'Header menu=1',
  `position_serial` int(11) NOT NULL,
  `status` int(11) NOT NULL,
  PRIMARY KEY (`cat_id`),
  UNIQUE KEY `slug` (`slug`)
) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_web_category`
--

INSERT INTO `dbt_web_category` VALUES (1,'home','Home',0,'','','',1,1,1),(2,'about','About',7,'public/uploads/b40e7e093d856ff3c5037421efade783.jpg','About Us','It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that',1,1,1),(3,'faq','F.A.Q',7,'public/uploads/46a46840f71102641160f82a1ef47044.jpg','Frequently Ask & Question','It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that',1,3,1),(4,'contact','Contact',7,'public/uploads/03d99f85c1b60a59fc101c26fb8a2b3e.jpg','Contact','It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that',1,5,1),(5,'terms','terms',8,'','','',0,2,1),(6,'privacy','privacy',0,'','','',0,0,1);

--
-- Table structure for table `dbt_web_language`
--

CREATE TABLE `dbt_web_language` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(256) DEFAULT NULL,
  `flag` varchar(256) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_web_language`
--

INSERT INTO `dbt_web_language` VALUES (1,'Français','fr');

--
-- Table structure for table `dbt_web_social_link`
--

CREATE TABLE `dbt_web_social_link` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(100) NOT NULL,
  `link` varchar(100) NOT NULL,
  `icon` varchar(100) NOT NULL,
  `status` int(11) NOT NULL,
  `date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `dbt_web_social_link`
--

INSERT INTO `dbt_web_social_link` VALUES (1,'Facebook','https://www.facebook.com','facebook',1,'2018-04-02 01:52:31'),(2,'twitter','https://twitter.com','twitter',1,'2018-04-02 01:29:25'),(3,'google plus','https://google-plus.com','google-plus',1,'2018-01-31 19:58:56'),(4,'youtube','https://www.youtube.com','fab fa-youtube',1,'2022-05-16 11:33:23'),(5,'instagram','https://instagram.com','instagram',1,'2022-05-17 05:00:20');

--
-- Table structure for table `dbt_web_subscriber`
--

CREATE TABLE `dbt_web_subscriber` (
  `sub_id` int(11) NOT NULL AUTO_INCREMENT,
  `email` varchar(100) NOT NULL,
  `status` int(11) NOT NULL,
  PRIMARY KEY (`sub_id`),
  UNIQUE KEY `email` (`email`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `dbt_web_subscriber`
--



